From: Carlos Maiolino <cem@kernel.org>
To: Yun Zhou <yun.zhou@windriver.com>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: move xfs_sync_sb_buf() out of libxfs into xfs_ioctl.c
Date: Mon, 05 Oct 2026 20:06:36 +0200 [thread overview]
Message-ID: <179122359604.102066.989822171795256366.b4-ty@kernel.org> (raw)
In-Reply-To: <20260916004335.228753-1-yun.zhou@windriver.com>
On Wed, 16 Sep 2026 08:43:35 +0800, Yun Zhou wrote:
> xfs_sync_sb_buf() dereferences mp->m_sb_bp and mp->m_rtsb_bp, which
> only exist in the kernel's struct xfs_mount, not in xfsprogs' libxfs.
> Keeping it in libxfs is a porting hazard.
>
> Its only caller, xfs_ioc_setlabel(), is kernel-only, so move it there
> and make it static.
>
> [...]
Applied to for-next, thanks!
[1/1] xfs: move xfs_sync_sb_buf() out of libxfs into xfs_ioctl.c
commit: 6654fca702b28b87cd365242498262080b1c223f
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-10-05 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 0:43 [PATCH] xfs: move xfs_sync_sb_buf() out of libxfs into xfs_ioctl.c Yun Zhou
2026-09-18 11:15 ` Christoph Hellwig
2026-10-05 18:06 ` Carlos Maiolino [this message]
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=179122359604.102066.989822171795256366.b4-ty@kernel.org \
--to=cem@kernel.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