From: David Hildenbrand <david@redhat.com>
To: Jan Kara <jack@suse.cz>, linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org,
Lorenzo Stoakes <lstoakes@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] mm: Do not reclaim private data from pinned page
Date: Tue, 2 May 2023 16:45:04 +0200 [thread overview]
Message-ID: <2bca2e69-6108-5595-3f5e-fbac3a93bab5@redhat.com> (raw)
In-Reply-To: <20230428124140.30166-1-jack@suse.cz>
On 28.04.23 14:41, Jan Kara wrote:
> If the page is pinned, there's no point in trying to reclaim it.
> Furthermore if the page is from the page cache we don't want to reclaim
> fs-private data from the page because the pinning process may be writing
> to the page at any time and reclaiming fs private info on a dirty page
> can upset the filesystem (see link below).
>
> Link: https://lore.kernel.org/linux-mm/20180103100430.GE4911@quack2.suse.cz
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> mm/vmscan.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> This was the non-controversial part of my series [1] dealing with pinned pages
> in filesystems. It is already a win as it avoids crashes in the filesystem and
> we can drop workarounds for this in ext4. Can we merge it please?
>
> [1] https://lore.kernel.org/all/20230209121046.25360-1-jack@suse.cz/
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index bf3eedf0209c..401a379ea99a 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -1901,6 +1901,16 @@ static unsigned int shrink_folio_list(struct list_head *folio_list,
> }
> }
>
> + /*
> + * Folio is unmapped now so it cannot be newly pinned anymore.
> + * No point in trying to reclaim folio if it is pinned.
> + * Furthermore we don't want to reclaim underlying fs metadata
> + * if the folio is pinned and thus potentially modified by the
> + * pinning process as that may upset the filesystem.
> + */
> + if (folio_maybe_dma_pinned(folio))
> + goto activate_locked;
> +
> mapping = folio_mapping(folio);
> if (folio_test_dirty(folio)) {
> /*
Acked-by: David Hildenbrand <david@redhat.com>
Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-05-02 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 12:41 Jan Kara
2023-04-28 12:58 ` Matthew Wilcox
2023-04-28 13:05 ` Lorenzo Stoakes
2023-04-29 4:50 ` Christoph Hellwig
2023-05-01 18:12 ` John Hubbard
2023-05-02 14:45 ` David Hildenbrand [this message]
2023-05-02 15:26 ` Peter Xu
2023-05-02 15:33 ` David Hildenbrand
2023-05-02 15:48 ` Peter Xu
2023-05-02 15:53 ` David Hildenbrand
2023-05-02 20:20 ` Andrew Morton
2023-05-03 9:51 ` Jan Kara
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=2bca2e69-6108-5595-3f5e-fbac3a93bab5@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.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