From: Luis Chamberlain <mcgrof@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: brauner@kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, riel@surriel.com,
willy@infradead.org, hannes@cmpxchg.org, oliver.sang@intel.com,
dave@stgolabs.net, david@redhat.com, axboe@kernel.dk,
hare@suse.de, david@fromorbit.com, djwong@kernel.org,
ritesh.list@gmail.com, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org, linux-mm@kvack.org,
gost.dev@samsung.com, p.raghav@samsung.com, da.gomez@samsung.com
Subject: Re: [PATCH 2/3] fs/buffer: avoid races with folio migrations on __find_get_block_slow()
Date: Wed, 2 Apr 2025 18:02:04 -0700 [thread overview]
Message-ID: <Z-3eDEBFK8md46-7@bombadil.infradead.org> (raw)
In-Reply-To: <lj6o73q6nev776uvy7potqrn5gmgtm4o2cev7dloedwasxcsmn@uanvqp3sm35p>
On Tue, Apr 01, 2025 at 12:57:37PM +0200, Jan Kara wrote:
> On Sat 29-03-25 23:47:31, Luis Chamberlain wrote:
> > diff --git a/fs/buffer.c b/fs/buffer.c
> > index c7abb4a029dc..a4e4455a6ce2 100644
> > --- a/fs/buffer.c
> > +++ b/fs/buffer.c
> > @@ -208,6 +208,15 @@ __find_get_block_slow(struct block_device *bdev, sector_t block)
> > head = folio_buffers(folio);
> > if (!head)
> > goto out_unlock;
> > +
> > + if (folio->mapping->a_ops->migrate_folio &&
> > + folio->mapping->a_ops->migrate_folio == buffer_migrate_folio_norefs) {
>
> This is always true for bdev mapping we have here, isn't it?
Yes, thanks!
> > + if (folio_test_lru(folio) &&
>
> Do you expect bdev page cache to contain non-LRU folios? I thought every
> pagecache folio is on LRU so this seems pointless as well? But I may be
> missing something here.
>
> > + folio_test_locked(folio) &&
> > + !folio_test_writeback(folio))
> > + goto out_unlock;
>
> I find this problematic. It fixes the race with migration, alright
> (although IMO we should have a comment very well explaining the interplay
> of folio lock and mapping->private_lock to make this work - probably in
> buffer_migrate_folio_norefs() - and reference it from here), but there are
> places which expect that if __find_get_block() doesn't return anything,
> this block is not cached in the buffer cache. And your change breaks this
> assumption.
Yup agreed!
Luis
next prev parent reply other threads:[~2025-04-03 1:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 6:47 [PATCH 0/3] mm: move migration work around to buffer-heads Luis Chamberlain
2025-03-30 6:47 ` [PATCH 1/3] mm/migrate: add might_sleep() on __migrate_folio() Luis Chamberlain
2025-03-30 12:04 ` Matthew Wilcox
2025-03-31 6:28 ` Luis Chamberlain
2025-04-01 22:53 ` Davidlohr Bueso
2025-03-30 6:47 ` [PATCH 2/3] fs/buffer: avoid races with folio migrations on __find_get_block_slow() Luis Chamberlain
2025-03-31 19:58 ` Luis Chamberlain
2025-04-02 23:11 ` Luis Chamberlain
2025-04-04 15:55 ` Luis Chamberlain
2025-04-01 10:57 ` Jan Kara
2025-04-01 21:49 ` Davidlohr Bueso
2025-04-02 1:58 ` Matthew Wilcox
2025-04-03 2:04 ` Luis Chamberlain
2025-04-03 13:43 ` Jan Kara
2025-04-03 16:11 ` Theodore Ts'o
2025-04-03 1:02 ` Luis Chamberlain [this message]
2025-03-30 6:47 ` [PATCH 3/3] mm/migrate: avoid atomic context on buffer_migrate_folio_norefs() migration Luis Chamberlain
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=Z-3eDEBFK8md46-7@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=da.gomez@samsung.com \
--cc=dave@stgolabs.net \
--cc=david@fromorbit.com \
--cc=david@redhat.com \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hannes@cmpxchg.org \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oliver.sang@intel.com \
--cc=p.raghav@samsung.com \
--cc=riel@surriel.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).