[lkml]   [2005]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH] Releasing resources with children
Releasing resources with children

What does it mean to release a resource with children? Should the
children become children of the released resource's parent? Should they
be released too? Should we fail the release?

I bet we have no callers who expect this right now, but with
insert_resource() we may get some. At the point where someone hits this
BUG we can figure out what semantics we want.

Signed-off-by: Matthew Wilcox <>

diff -urpNX dontdiff linux-2.6.11-bk10/kernel/resource.c parisc-2.6-bk/kernel/resource.c
--- linux-2.6.11-bk10/kernel/resource.c 2005-03-14 06:44:08.205342005 -0700
+++ parisc-2.6-bk/kernel/resource.c 2005-03-14 07:07:54.000000000 -0700
@@ -181,6 +181,8 @@ static int __release_resource(struct res
struct resource *tmp, **p;

+ BUG_ON(old->child);
p = &old->parent->child;
for (;;) {
tmp = *p;
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at
 \ /
  Last update: 2005-03-22 14:11    [W:0.032 / U:3.496 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site