From: Yu Zhao <yuzhao@google.com>
To: Mauricio Faria de Oliveira <mfo@canonical.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>,
linux-mm@kvack.org, linux-block@vger.kernel.org,
Huang Ying <ying.huang@intel.com>,
Miaohe Lin <linmiaohe@huawei.com>, Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH v2] mm: fix race between MADV_FREE reclaim and blkdev direct IO read
Date: Mon, 10 Jan 2022 23:48:13 -0700 [thread overview]
Message-ID: <Yd0oLWtVAyAexyQc@google.com> (raw)
In-Reply-To: <20220105233440.63361-1-mfo@canonical.com>
On Wed, Jan 05, 2022 at 08:34:40PM -0300, Mauricio Faria de Oliveira wrote:
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 163ac4e6bcee..8671de473c25 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1570,7 +1570,20 @@ static bool try_to_unmap_one(struct page *page, struct vm_area_struct *vma,
>
> /* MADV_FREE page check */
> if (!PageSwapBacked(page)) {
> - if (!PageDirty(page)) {
> + int ref_count = page_ref_count(page);
> + int map_count = page_mapcount(page);
> +
> + /*
> + * The only page refs must be from the isolation
> + * (checked by the caller shrink_page_list() too)
> + * and one or more rmap's (dropped by discard:).
> + *
> + * Check the reference count before dirty flag
> + * with memory barrier; see __remove_mapping().
> + */
> + smp_rmb();
> + if ((ref_count - 1 == map_count) &&
> + !PageDirty(page)) {
> /* Invalidate as we cleared the pte */
> mmu_notifier_invalidate_range(mm,
> address, address + PAGE_SIZE);
Out of curiosity, how does it work with COW in terms of reordering?
Specifically, it seems to me get_page() and page_dup_rmap() in
copy_present_pte() can happen in any order, and if page_dup_rmap()
is seen first, and direct io is holding a refcnt, this check can still
pass?
next prev parent reply other threads:[~2022-01-11 6:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 23:34 Mauricio Faria de Oliveira
2022-01-06 23:15 ` Minchan Kim
2022-01-07 0:11 ` Yang Shi
2022-01-07 1:08 ` Yang Shi
2022-01-11 1:34 ` Huang, Ying
2022-01-11 6:48 ` Yu Zhao [this message]
2022-01-11 18:54 ` Minchan Kim
2022-01-11 19:29 ` John Hubbard
2022-01-11 20:20 ` Minchan Kim
2022-01-11 20:21 ` Minchan Kim
2022-01-11 21:59 ` Minchan Kim
2022-01-11 23:38 ` John Hubbard
2022-01-12 0:01 ` Minchan Kim
2022-01-12 1:46 ` Huang, Ying
2022-01-12 17:33 ` Minchan Kim
2022-01-12 21:53 ` Mauricio Faria de Oliveira
2022-01-12 22:37 ` Minchan Kim
2022-01-13 8:54 ` Huang, Ying
2022-01-13 12:30 ` Huang, Ying
2022-01-13 14:54 ` Mauricio Faria de Oliveira
2022-01-13 14:30 ` Mauricio Faria de Oliveira
2022-01-13 7:29 ` Yu Zhao
2022-01-14 0:35 ` Minchan Kim
2022-01-31 23:10 ` Mauricio Faria de Oliveira
2022-01-13 5:47 ` Huang, Ying
2022-01-13 6:37 ` Miaohe Lin
2022-01-13 8:04 ` Huang, Ying
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=Yd0oLWtVAyAexyQc@google.com \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mfo@canonical.com \
--cc=minchan@kernel.org \
--cc=shy828301@gmail.com \
--cc=ying.huang@intel.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