From: "Huang, Ying" <ying.huang@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Data corruption problem with swapfiles and THP
Date: Fri, 13 Aug 2021 08:21:38 +0800 [thread overview]
Message-ID: <87a6lm6vot.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <YRU5NAD+G9DVFYM/@casper.infradead.org> (Matthew Wilcox's message of "Thu, 12 Aug 2021 16:07:32 +0100")
Matthew Wilcox <willy@infradead.org> writes:
> There is an assumption in the swap writepage path that a THP is physically
> contiguous on swap:
>
> bio->bi_iter.bi_sector = swap_page_sector(page);
> bio->bi_opf = REQ_OP_WRITE | REQ_SWAP | wbc_to_write_flags(wbc);
> bio->bi_end_io = end_write_func;
> bio_add_page(bio, page, thp_size(page), 0);
>
> As far as I can tell, this is not necessarily true. If a file is not
> contiguous, we can have an extent which is 1MB long followed by an extent
> somewhere else on storage that's 1MB long. When we try to write a 2MB
> page to swap, we overwrite whatever's on the block device after that
> first 1MB extent.
>
> (Came across this by code examination while looking at getting rid of
> the bio path entirely; no attempt has been made to produce this problem;
> something else may prevent it from actually happening)
Yes. THP needs to be split firstly before swapping out to a swap device
backed by a file. Please take a look at the get_swap_pages()
if (size == SWAPFILE_CLUSTER) {
if (si->flags & SWP_BLKDEV)
n_ret = swap_alloc_cluster(si, swp_entries);
} else
n_ret = scan_swap_map_slots(si, SWAP_HAS_CACHE,
n_goal, swp_entries);
If the swap device is backed by a file, si->flags & SWP_BLKDEV == 0,
only normal swap entry (not huge) can be allocated. This will result
that the THP is split.
Best Regards,
Huang, Ying
prev parent reply other threads:[~2021-08-13 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 15:07 Matthew Wilcox
2021-08-13 0:21 ` Huang, Ying [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=87a6lm6vot.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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