The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Possibly bug in radix_tree_delete, and fix.
Date: Thu, 16 Feb 2006 14:16:31 +1100	[thread overview]
Message-ID: <43F3EE8F.8060000@yahoo.com.au> (raw)
In-Reply-To: <17395.58244.839605.685011@cse.unsw.edu.au>

Neil Brown wrote:
> Hi Nick,
>  I believe there is a bug in radix_tree_delete introduced by:
> 
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d5274261ea46f0aae93820fe36628249120d2f75
> 
> The nature of the bug is that if a tag is set on a node that is being
> deleted, then that tag is unconditionally cleared in the parent of the
> node, even if the deleted node has siblings with the tag still set.
> 
> I don't know what the large-scale consequences of this bug might be,
> but I'm kinda hoping fixing it will fix a nasty NFS client related
> oops we are seeing in radix_tree_tag_set ....
> 

I think you're right. I was kind of suspecting I might have introduced
a silly bug somewhere after a couple of radix tree oopses popped up.

Not sure why it didn't trigger Andrew's test suite, but I guess that's
something to add.

> My suggested patch is below.
> 
> Please review, confirm, and Ack:
> 

It should be basically an identical block to the one below in the main
loop, yeah? You're missing the nr_cleared_tags bit.

Something like:

    tags[tag] = 1;
    if (tag_get(pathp->node, tag, pathp->offset)) {
       tag_clear(pathp->node, tag, pathp->offset);
       if (!any_tag_set(pathp->node, tag)) {
          tags[tag] = 0;
          nr_cleared_tags++;
       }
    }

And you can add an
Acked-by: Nick Piggin <npiggin@suse.de>

Thanks,
Nick

> Thanks,
> NeilBrown
> 
> 
> Fix over-zealous clearing of tags in radix_tree_delete.
> 
> Signed-off-by: Neil Brown <neilb@suse.de>
> 
> ### Diffstat output
>  ./lib/radix-tree.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff ./lib/radix-tree.c~current~ ./lib/radix-tree.c
> --- ./lib/radix-tree.c~current~	2006-02-16 13:22:28.000000000 +1100
> +++ ./lib/radix-tree.c	2006-02-16 13:23:19.000000000 +1100
> @@ -755,7 +755,7 @@ void *radix_tree_delete(struct radix_tre
>  	for (tag = 0; tag < RADIX_TREE_TAGS; tag++) {
>  		if (tag_get(pathp->node, tag, pathp->offset)) {
>  			tag_clear(pathp->node, tag, pathp->offset);
> -			tags[tag] = 0;
> +			tags[tag] = any_tag_set(pathp->node, tag);
>  			nr_cleared_tags++;
>  		} else
>  			tags[tag] = 1;
> 


-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-02-16  3:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16  2:29 Possibly bug in radix_tree_delete, and fix Neil Brown
2006-02-16  3:16 ` Nick Piggin [this message]
2006-02-16  3:48   ` Neil Brown
2006-02-16  3:55   ` Andrew Morton
2006-02-16  5:08     ` Nick Piggin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43F3EE8F.8060000@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox