From: Shaohua Li <shli@kernel.org>
To: linux-mm@kvack.org
Cc: hughd@google.com, riel@redhat.com, minchan@kernel.org,
kmpark@infradead.org
Subject: [patch 2/4 v3]swap: __swap_duplicate check bad swap entry
Date: Thu, 21 Feb 2013 10:22:19 +0800 [thread overview]
Message-ID: <20130221022219.GE32580@kernel.org> (raw)
Sorry if you receive this one twice, last mail get mail address messed.
In swapin_readahead(), read_swap_cache_async() can read a bad swap entry,
because we don't check if readahead swap entry is bad. This doesn't break
anything but such swapin page is wasteful and can only be freed at page
reclaim. We avoid read such swap entry.
And next patch will mark a swap entry bad temporarily for discard. Without this
patch, swap entry count will be messed.
Thanks Hugh to inspire swapin_readahead could use bad swap entry.
Signed-off-by: Shaohua Li <shli@fusionio.com>
---
mm/swapfile.c | 5 +++++
1 file changed, 5 insertions(+)
Index: linux/mm/swapfile.c
===================================================================
--- linux.orig/mm/swapfile.c 2013-02-18 15:21:09.285317914 +0800
+++ linux/mm/swapfile.c 2013-02-18 15:21:34.545004083 +0800
@@ -2374,6 +2374,11 @@ static int __swap_duplicate(swp_entry_t
goto unlock_out;
count = p->swap_map[offset];
+ if (unlikely(swap_count(count) == SWAP_MAP_BAD)) {
+ err = -ENOENT;
+ goto unlock_out;
+ }
+
has_cache = count & SWAP_HAS_CACHE;
count &= ~SWAP_HAS_CACHE;
err = 0;
--
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 reply other threads:[~2013-02-21 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 2:22 Shaohua Li [this message]
2013-03-12 1:45 ` [patch 2/4 v3]swap: __swap_duplicate check bad swap entry Rafael Aquini
[not found] <20130221021738.GB32580@kernel.org>
2013-03-19 21:34 ` Hugh Dickins
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=20130221022219.GE32580@kernel.org \
--to=shli@kernel.org \
--cc=hughd@google.com \
--cc=kmpark@infradead.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
/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).