From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: jack@suse.cz, hch@lst.de, nickpiggin@yahoo.com.au
Subject: + lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update.patch added to -mm tree
Date: Wed, 18 Aug 2010 11:47:18 -0700 [thread overview]
Message-ID: <201008181847.o7IIlIHG005840@imap1.linux-foundation.org> (raw)
The patch titled
lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update
has been added to the -mm tree. Its filename is
lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update
From: Jan Kara <jack@suse.cz>
below is an updated version of the fix. The core of the fix is the same,
it just includes a few more comments updates and a check in
tag_pages_for_writeback() to avoid cycling indefinitely.
Signed-off-by: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/radix-tree.c | 2 ++
mm/page-writeback.c | 3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff -puN lib/radix-tree.c~lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update lib/radix-tree.c
--- a/lib/radix-tree.c~lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update
+++ a/lib/radix-tree.c
@@ -625,6 +625,8 @@ EXPORT_SYMBOL(radix_tree_tag_get);
*
* The function returns number of leaves where the tag was set and sets
* *first_indexp to the first unscanned index.
+ * WARNING! *first_indexp can wrap if last_index is ULONG_MAX. Caller must
+ * be prepared to handle that.
*/
unsigned long radix_tree_range_tag_if_tagged(struct radix_tree_root *root,
unsigned long *first_indexp, unsigned long last_index,
diff -puN mm/page-writeback.c~lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update mm/page-writeback.c
--- a/mm/page-writeback.c~lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update
+++ a/mm/page-writeback.c
@@ -836,7 +836,8 @@ void tag_pages_for_writeback(struct addr
spin_unlock_irq(&mapping->tree_lock);
WARN_ON_ONCE(tagged > WRITEBACK_TAG_BATCH);
cond_resched();
- } while (tagged >= WRITEBACK_TAG_BATCH);
+ /* We check 'start' to handle wrapping when end == ~0UL */
+ } while (tagged >= WRITEBACK_TAG_BATCH && start);
}
EXPORT_SYMBOL(tag_pages_for_writeback);
_
Patches currently in -mm which might be from jack@suse.cz are
origin.patch
lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged.patch
lib-radix-treec-fix-overflow-in-radix_tree_range_tag_if_tagged-update.patch
linux-next.patch
aio-do-not-return-erestartsys-and-friends-from-aio.patch
reiser4.patch
reply other threads:[~2010-08-18 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201008181847.o7IIlIHG005840@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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