From: Wu Fengguang <fengguang.wu@intel.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Trivial Patch Monkey <trivial@kernel.org>,
Nick Piggin <npiggin@suse.de>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] radix-tree: document wrap-around issue of radix_tree_next_hole()
Date: Thu, 27 Nov 2008 19:39:26 +0800 [thread overview]
Message-ID: <20081127113926.GA28636@localhost> (raw)
In-Reply-To: <alpine.LNX.1.10.0811271137240.19853@jikos.suse.cz>
On Thu, Nov 27, 2008 at 12:38:06PM +0200, Jiri Kosina wrote:
> On Sun, 23 Nov 2008, Wu Fengguang wrote:
>
> > And some 80-line cleanups.
> >
> > Signed-off-by: Wu Fengguang <wfg@linux.intel.com>
> > ---
> > lib/radix-tree.c | 11 ++++++-----
> > 1 file changed, 6 insertions(+), 5 deletions(-)
> >
> > --- linux-2.6.orig/lib/radix-tree.c
> > +++ linux-2.6/lib/radix-tree.c
> > @@ -640,13 +640,14 @@ EXPORT_SYMBOL(radix_tree_tag_get);
> > *
> > * Returns: the index of the hole if found, otherwise returns an index
> > * outside of the set specified (in which case 'return - index >= max_scan'
> > - * will be true).
> > + * will be true). In rare cases of index wrap-around, 0 will be returned.
> > *
> > * radix_tree_next_hole may be called under rcu_read_lock. However, like
> > - * radix_tree_gang_lookup, this will not atomically search a snapshot of the
> > - * tree at a single point in time. For example, if a hole is created at index
> > - * 5, then subsequently a hole is created at index 10, radix_tree_next_hole
> > - * covering both indexes may return 10 if called under rcu_read_lock.
> > + * radix_tree_gang_lookup, this will not atomically search a snapshot of
> > + * the tree at a single point in time. For example, if a hole is created
> > + * at index 5, then subsequently a hole is created at index 10,
> > + * radix_tree_next_hole covering both indexes may return 10 if called
> > + * under rcu_read_lock.
> > */
> > unsigned long radix_tree_next_hole(struct radix_tree_root *root,
> > unsigned long index, unsigned long max_scan)
> >
>
> I don't see this applied in any of the publically visible trees, so I have
> taken this into -trivial. Please let me know if it has been through any
> other channel already.
OK, thank you.
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-11-27 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 10:51 Wu Fengguang
2008-11-27 10:38 ` Jiri Kosina
2008-11-27 11:39 ` Wu Fengguang [this message]
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=20081127113926.GA28636@localhost \
--to=fengguang.wu@intel.com \
--cc=jkosina@suse.cz \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=trivial@kernel.org \
/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