linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: jack@suse.cz, tytso@mit.edu, adilger.kernel@dilger.ca,
	 brauner@kernel.org, mcgrof@kernel.org, willy@infradead.org,
	hare@suse.de,  djwong@kernel.org, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,  linux-mm@kvack.org,
	kernel test robot <oliver.sang@intel.com>,
	 syzbot+f3c6fda1297c748a7076@syzkaller.appspotmail.com
Subject: Re: [PATCH 7/7] mm/migrate: fix sleep in atomic for large folios and buffer heads
Date: Wed, 16 Apr 2025 11:43:08 +0200	[thread overview]
Message-ID: <4qdxc5vwmf3squ4yjpgarxdss3d7sacfwgupf4o3onbqxjzb23@4i4ubrmoi74r> (raw)
In-Reply-To: <20250415231635.83960-8-dave@stgolabs.net>

On Tue 15-04-25 16:16:35, Davidlohr Bueso wrote:
> The large folio + buffer head noref migration scenarios are
> being naughty and blocking while holding a spinlock.
> 
> As a consequence of the pagecache lookup path taking the
> folio lock this serializes against migration paths, so
> they can wait for each other. For the private_lock
> atomic case, a new BH_Migrate flag is introduced which
> enables the lookup to bail.
> 
> This allows the critical region of the private_lock on
> the migration path to be reduced to the way it was before
> ebdf4de5642fb6 ("mm: migrate: fix reference  check race
> between __find_get_block() and migration"), that is covering
> the count checks.
> 
> The scope is always noref migration.
> 
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Reported-by: syzbot+f3c6fda1297c748a7076@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/oe-lkp/202503101536.27099c77-lkp@intel.com
> Fixes: 3c20917120ce61 ("block/bdev: enable large folio support for large logical block sizes")
> Co-developed-by: Luis Chamberlain <mcgrof@kernel.org>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>

Looks good! Feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  fs/buffer.c                 | 12 +++++++++++-
>  fs/ext4/ialloc.c            |  3 ++-
>  include/linux/buffer_head.h |  1 +
>  mm/migrate.c                |  8 +++++---
>  4 files changed, 19 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/buffer.c b/fs/buffer.c
> index f8e63885604b..b8e1e6e325cd 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -207,6 +207,15 @@ __find_get_block_slow(struct block_device *bdev, sector_t block, bool atomic)
>  	head = folio_buffers(folio);
>  	if (!head)
>  		goto out_unlock;
> +	/*
> +	 * Upon a noref migration, the folio lock serializes here;
> +	 * otherwise bail.
> +	 */
> +	if (test_bit_acquire(BH_Migrate, &head->b_state)) {
> +		WARN_ON(!atomic);
> +		goto out_unlock;
> +	}
> +
>  	bh = head;
>  	do {
>  		if (!buffer_mapped(bh))
> @@ -1390,7 +1399,8 @@ lookup_bh_lru(struct block_device *bdev, sector_t block, unsigned size)
>  /*
>   * Perform a pagecache lookup for the matching buffer.  If it's there, refresh
>   * it in the LRU and mark it as accessed.  If it is not present then return
> - * NULL
> + * NULL. Atomic context callers may also return NULL if the buffer is being
> + * migrated; similarly the page is not marked accessed either.
>   */
>  static struct buffer_head *
>  find_get_block_common(struct block_device *bdev, sector_t block,
> diff --git a/fs/ext4/ialloc.c b/fs/ext4/ialloc.c
> index 38bc8d74f4cc..e7ecc7c8a729 100644
> --- a/fs/ext4/ialloc.c
> +++ b/fs/ext4/ialloc.c
> @@ -691,7 +691,8 @@ static int recently_deleted(struct super_block *sb, ext4_group_t group, int ino)
>  	if (!bh || !buffer_uptodate(bh))
>  		/*
>  		 * If the block is not in the buffer cache, then it
> -		 * must have been written out.
> +		 * must have been written out, or, most unlikely, is
> +		 * being migrated - false failure should be OK here.
>  		 */
>  		goto out;
>  
> diff --git a/include/linux/buffer_head.h b/include/linux/buffer_head.h
> index c791aa9a08da..0029ff880e27 100644
> --- a/include/linux/buffer_head.h
> +++ b/include/linux/buffer_head.h
> @@ -34,6 +34,7 @@ enum bh_state_bits {
>  	BH_Meta,	/* Buffer contains metadata */
>  	BH_Prio,	/* Buffer should be submitted with REQ_PRIO */
>  	BH_Defer_Completion, /* Defer AIO completion to workqueue */
> +	BH_Migrate,     /* Buffer is being migrated (norefs) */
>  
>  	BH_PrivateStart,/* not a state bit, but the first bit available
>  			 * for private allocation by other entities
> diff --git a/mm/migrate.c b/mm/migrate.c
> index 6e2488e5dbe4..c80591514e66 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -845,9 +845,11 @@ static int __buffer_migrate_folio(struct address_space *mapping,
>  		return -EAGAIN;
>  
>  	if (check_refs) {
> -		bool busy;
> +		bool busy, migrating;
>  		bool invalidated = false;
>  
> +		migrating = test_and_set_bit_lock(BH_Migrate, &head->b_state);
> +		VM_WARN_ON_ONCE(migrating);
>  recheck_buffers:
>  		busy = false;
>  		spin_lock(&mapping->i_private_lock);
> @@ -859,12 +861,12 @@ static int __buffer_migrate_folio(struct address_space *mapping,
>  			}
>  			bh = bh->b_this_page;
>  		} while (bh != head);
> +		spin_unlock(&mapping->i_private_lock);
>  		if (busy) {
>  			if (invalidated) {
>  				rc = -EAGAIN;
>  				goto unlock_buffers;
>  			}
> -			spin_unlock(&mapping->i_private_lock);
>  			invalidate_bh_lrus();
>  			invalidated = true;
>  			goto recheck_buffers;
> @@ -883,8 +885,7 @@ static int __buffer_migrate_folio(struct address_space *mapping,
>  
>  unlock_buffers:
>  	if (check_refs)
> -		spin_unlock(&mapping->i_private_lock);
> +		clear_bit_unlock(BH_Migrate, &head->b_state);
>  	bh = head;
>  	do {
>  		unlock_buffer(bh);
> --
> 2.39.5
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR


  reply	other threads:[~2025-04-16  9:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 23:16 [PATCH -next 0/7] fs/buffer: split pagecache lookups into atomic or blocking Davidlohr Bueso
2025-04-15 23:16 ` [PATCH 1/7] fs/buffer: split locking for pagecache lookups Davidlohr Bueso
2025-04-16  9:32   ` Jan Kara
2025-04-15 23:16 ` [PATCH 2/7] fs/buffer: introduce sleeping flavors " Davidlohr Bueso
2025-04-16  9:33   ` Jan Kara
2025-04-15 23:16 ` [PATCH 3/7] fs/buffer: use sleeping version of __find_get_block() Davidlohr Bueso
2025-04-16  9:33   ` Jan Kara
2025-04-15 23:16 ` [PATCH 4/7] fs/ocfs2: " Davidlohr Bueso
2025-04-16  9:35   ` Jan Kara
2025-04-15 23:16 ` [PATCH 5/7] fs/jbd2: " Davidlohr Bueso
2025-04-16  9:38   ` Jan Kara
2025-04-15 23:16 ` [PATCH 6/7] fs/ext4: use sleeping version of sb_find_get_block() Davidlohr Bueso
2025-04-16  9:39   ` Jan Kara
2025-04-15 23:16 ` [PATCH 7/7] mm/migrate: fix sleep in atomic for large folios and buffer heads Davidlohr Bueso
2025-04-16  9:43   ` Jan Kara [this message]
2025-04-16 19:27 ` [PATCH -next 0/7] fs/buffer: split pagecache lookups into atomic or blocking Luis Chamberlain
2025-04-17  9:57   ` Christian Brauner
2025-04-22 11:25   ` Jan Kara
2025-04-17  9:58 ` Christian Brauner
2025-04-18  1:59 [PATCH v2 " Davidlohr Bueso
2025-04-18  1:59 ` [PATCH 7/7] mm/migrate: fix sleep in atomic for large folios and buffer heads Davidlohr Bueso

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=4qdxc5vwmf3squ4yjpgarxdss3d7sacfwgupf4o3onbqxjzb23@4i4ubrmoi74r \
    --to=jack@suse.cz \
    --cc=adilger.kernel@dilger.ca \
    --cc=brauner@kernel.org \
    --cc=dave@stgolabs.net \
    --cc=djwong@kernel.org \
    --cc=hare@suse.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=oliver.sang@intel.com \
    --cc=syzbot+f3c6fda1297c748a7076@syzkaller.appspotmail.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