Skip to contentSkip to conversation

__release_region() race

PATCH In review MAEDA Naoaki 2 participants 2 messages Feb 12, 2004

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 __release_region() race

Hi,

I am testing PCI hot-plug in 2.6.2 kernel, but sometimes a struct resource tree in kernel/resource.c was broken if multiple hot-plug requests are issued at the same time.

The reason is lots of drivers call release_region() on hot removal, and __release_region(), which is invoked by release_region() macro, changes the tree without holding a writer lock for resource_lock.

I think __release_region() must hold a writer lock as well as __request_region() does.

A following patch fixes the issue in my environment.

Regards,
Naoaki Maeda

kernel/resource.c +6 -0
diff -Naur linux-2.6.3-rc2.org/kernel/resource.c linux-2.6.3-rc2/kernel/resource.c
@@ -475,6 +475,8 @@
 	p = &parent->child;
 	end = start + n - 1;
 
+	write_lock(&resource_lock);
+
 	for (;;) {
 		struct resource *res = *p;
 
@@ -488,11 +490,15 @@
 			if (res->start != start || res->end != end)
 				break;
 			*p = res->sibling;
+			write_unlock(&resource_lock);
 			kfree(res);
 			return;
 		}
 		p = &res->sibling;
 	}
+
+	write_unlock(&resource_lock);
+
 	printk(KERN_WARNING "Trying to free nonexistent resource <%08lx-%08lx>\n", start, end);
 }
 
#1 lore raw
Quoted 3 lines · MAEDA Naoaki

I think __release_region() must hold a writer lock as well as
__request_region() does.

Me too. Thanks.