From: Wu Fengguang <fengguang.wu@intel.com>
To: Cesar Eduardo Barros <cesarb@cesarb.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] radix-tree: fix radix_tree_prev_hole underflow case
Date: Fri, 14 May 2010 10:15:08 +0800 [thread overview]
Message-ID: <20100514021508.GA7810@localhost> (raw)
In-Reply-To: <1273802724-3414-1-git-send-email-cesarb@cesarb.net>
On Fri, May 14, 2010 at 10:05:24AM +0800, Cesar Eduardo Barros wrote:
> radix_tree_prev_hole() used LONG_MAX to detect underflow; however,
> ULONG_MAX is clearly what was intended, both here and by its only user
> (count_history_pages at mm/readahead.c).
Good catch, thanks! I actually have a more smart
radix_tree_prev_hole() that uses ULONG_MAX.
Andrew, fortunately this bug has little impact on readahead.
Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
> Cc: Wu Fengguang <fengguang.wu@intel.com>
> Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.net>
> ---
> lib/radix-tree.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/radix-tree.c b/lib/radix-tree.c
> index b69031f..be40980 100644
> --- a/lib/radix-tree.c
> +++ b/lib/radix-tree.c
> @@ -656,7 +656,7 @@ EXPORT_SYMBOL(radix_tree_next_hole);
> *
> * Returns: the index of the hole if found, otherwise returns an index
> * outside of the set specified (in which case 'index - return >= max_scan'
> - * will be true). In rare cases of wrap-around, LONG_MAX will be returned.
> + * will be true). In rare cases of wrap-around, ULONG_MAX 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
> @@ -674,7 +674,7 @@ unsigned long radix_tree_prev_hole(struct radix_tree_root *root,
> if (!radix_tree_lookup(root, index))
> break;
> index--;
> - if (index == LONG_MAX)
> + if (index == ULONG_MAX)
> break;
> }
>
> --
> 1.6.6.1
--
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>
next prev parent reply other threads:[~2010-05-14 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 2:05 [PATCH] radix-tree: fix radix_tree_prev_hole underflow case Cesar Eduardo Barros
2010-05-14 2:15 ` Wu Fengguang [this message]
2010-05-14 2:28 ` Cesar Eduardo Barros
2010-05-14 2:37 ` Wu Fengguang
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=20100514021508.GA7810@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).