From: "Darrick J. Wong" <djwong@kernel.org>
To: Yun Zhou <yun.zhou@windriver.com>
Cc: cem@kernel.org, hch@infradead.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf
Date: Mon, 13 Jul 2026 15:04:36 -0700 [thread overview]
Message-ID: <20260713220436.GH7195@frogsfrogsfrogs> (raw)
In-Reply-To: <20260713145002.1627608-1-yun.zhou@windriver.com>
On Mon, Jul 13, 2026 at 10:50:02PM +0800, Yun Zhou wrote:
> xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous
> xfs_trans_commit(), which flushes the CIL push workqueue internally.
> If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to
> lock these buffers to fail them, causing a deadlock:
>
> setlabel: holds buf lock -> flush_workqueue(xfs-cil)
> CIL push worker: xfs_buf_item_unpin -> xfs_buf_lock(same buf)
>
> Remove the xfs_trans_bhold() calls so that commit releases the buffer
> locks normally. After the sync commit, re-acquire the buffers via
> mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.
Is there a risk of writing out the wrong superblock contents if
something else grabs the buffer lock(s) between the xfs_trans_commit and
the xfs_buf_lock calls? Can we walk off a garbage
xfs_mount::m_{rt,}sb_bp pointer if the filesystem is being torn down, or
does something prevent that?
--D
> Fixes: f7664b31975b ("xfs: implement online get/set fs label")
> Reported-by: syzbot+837bcd54843dd6262f2f@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=837bcd54843dd6262f2f
> Signed-off-by: Yun Zhou <yun.zhou@windriver.com>
> ---
> fs/xfs/libxfs/xfs_sb.c | 37 +++++++++++++++++++------------------
> 1 file changed, 19 insertions(+), 18 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_sb.c b/fs/xfs/libxfs/xfs_sb.c
> index 47322adb7690..fbb4505b1e9e 100644
> --- a/fs/xfs/libxfs/xfs_sb.c
> +++ b/fs/xfs/libxfs/xfs_sb.c
> @@ -1471,7 +1471,6 @@ xfs_sync_sb_buf(
> {
> struct xfs_trans *tp;
> struct xfs_buf *bp;
> - struct xfs_buf *rtsb_bp = NULL;
> int error;
>
> error = xfs_trans_alloc(mp, &M_RES(mp)->tr_sb, 0, 0, 0, &tp);
> @@ -1480,26 +1479,28 @@ xfs_sync_sb_buf(
>
> bp = xfs_trans_getsb(tp);
> xfs_log_sb(tp);
> - xfs_trans_bhold(tp, bp);
> - if (update_rtsb) {
> - rtsb_bp = xfs_log_rtsb(tp, bp);
> - if (rtsb_bp)
> - xfs_trans_bhold(tp, rtsb_bp);
> - }
> + if (update_rtsb)
> + xfs_log_rtsb(tp, bp);
> xfs_trans_set_sync(tp);
> error = xfs_trans_commit(tp);
> if (error)
> - goto out;
> - /*
> - * write out the sb buffer to get the changes to disk
> - */
> - error = xfs_bwrite(bp);
> - if (!error && rtsb_bp)
> - error = xfs_bwrite(rtsb_bp);
> -out:
> - if (rtsb_bp)
> - xfs_buf_relse(rtsb_bp);
> - xfs_buf_relse(bp);
> + return error;
> +
> + /* Re-acquire and write the sb and rtsb to disk. */
> + xfs_buf_lock(mp->m_sb_bp);
> + xfs_buf_hold(mp->m_sb_bp);
> + error = xfs_bwrite(mp->m_sb_bp);
> + xfs_buf_relse(mp->m_sb_bp);
> + if (error)
> + return error;
> +
> + if (update_rtsb && mp->m_rtsb_bp) {
> + xfs_buf_lock(mp->m_rtsb_bp);
> + xfs_buf_hold(mp->m_rtsb_bp);
> + error = xfs_bwrite(mp->m_rtsb_bp);
> + xfs_buf_relse(mp->m_rtsb_bp);
> + }
> +
> return error;
> }
>
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-07-13 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 14:50 [PATCH] xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf Yun Zhou
2026-07-13 22:04 ` Darrick J. Wong [this message]
2026-07-14 1:41 ` Zhou, Yun
2026-07-14 17:46 ` Darrick J. Wong
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=20260713220436.GH7195@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yun.zhou@windriver.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