mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: Yun Zhou <yun.zhou@windriver.com>
Cc: djwong@kernel.org, hch@infradead.org, linux-xfs@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: fix compilation warnings in xfs_sync_sb_buf when CONFIG_XFS_RT=n
Date: Wed, 22 Jul 2026 10:49:03 +0200	[thread overview]
Message-ID: <amCBowU-Q-QrGYoX@andromeda.toxiclabs.cc> (raw)
In-Reply-To: <20260722042841.220534-1-yun.zhou@windriver.com>

On Wed, Jul 22, 2026 at 12:28:41PM +0800, Yun Zhou wrote:
> When CONFIG_XFS_RT is disabled, xfs_log_rtsb() is a macro expanding to
> (NULL), causing 'statement with no effect' and 'variable set but not
> used' warnings.
> 
> Fix by removing the bp variable and passing xfs_trans_getsb(tp) directly
> to xfs_log_rtsb().  This is safe because xfs_log_sb() already joins the
> sb buffer to the transaction internally.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202607212237.Pzw1sr5k-lkp@intel.com/
> Fixes: b9ad0b9891dd ("xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf")
> Signed-off-by: Yun Zhou <yun.zhou@windriver.com>

We don't need a fix for a patch that is still in linux-next... Merge it
against your original patch and re-send it. I'll just replace the old
patch


> ---
>  fs/xfs/libxfs/xfs_sb.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_sb.c b/fs/xfs/libxfs/xfs_sb.c
> index fbb4505b1e9e..c4fa7fb0e39a 100644
> --- a/fs/xfs/libxfs/xfs_sb.c
> +++ b/fs/xfs/libxfs/xfs_sb.c
> @@ -1470,17 +1470,15 @@ xfs_sync_sb_buf(
>  	bool			update_rtsb)
>  {
>  	struct xfs_trans	*tp;
> -	struct xfs_buf		*bp;
>  	int			error;
>  
>  	error = xfs_trans_alloc(mp, &M_RES(mp)->tr_sb, 0, 0, 0, &tp);
>  	if (error)
>  		return error;
>  
> -	bp = xfs_trans_getsb(tp);
>  	xfs_log_sb(tp);
>  	if (update_rtsb)
> -		xfs_log_rtsb(tp, bp);
> +		(void)xfs_log_rtsb(tp, xfs_trans_getsb(tp));
>  	xfs_trans_set_sync(tp);
>  	error = xfs_trans_commit(tp);
>  	if (error)
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2026-07-22  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  4:28 Yun Zhou
2026-07-22  8:49 ` Carlos Maiolino [this message]
2026-07-22  8:58   ` Christoph Hellwig
2026-07-22  9:22     ` Zhou, Yun
2026-07-22  9:11   ` Zhou, Yun

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=amCBowU-Q-QrGYoX@andromeda.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=djwong@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

all inboxes | Powered by JetHome®