From: Christian Brauner <brauner@kernel.org>
To: Xichao Zhao <zhao.xichao@vivo.com>
Cc: Christian Brauner <brauner@kernel.org>,
jack@suse.cz, gnoack@google.com, linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
mic@digikod.net
Subject: Re: [PATCH] fs: Replace offsetof() with struct_size() in ioctl_file_dedupe_range()
Date: Fri, 29 Aug 2025 12:01:20 +0200 [thread overview]
Message-ID: <20250829-passierbar-losen-cd47a4b68c3d@brauner> (raw)
In-Reply-To: <20250829091510.597858-1-zhao.xichao@vivo.com>
On Fri, 29 Aug 2025 17:15:10 +0800, Xichao Zhao wrote:
> When dealing with structures containing flexible arrays, struct_size()
> provides additional compile-time checks compared to offsetof(). This
> enhances code robustness and reduces the risk of potential errors.
>
>
Applied to the vfs-6.18.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.18.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.18.misc
[1/1] fs: Replace offsetof() with struct_size() in ioctl_file_dedupe_range()
https://git.kernel.org/vfs/vfs/c/38d1227fa71d
prev parent reply other threads:[~2025-08-29 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 9:15 [PATCH] fs: Replace offsetof() with struct_size() in ioctl_file_dedupe_range() Xichao Zhao
2025-08-29 9:27 ` Jan Kara
2025-08-29 10:01 ` Christian Brauner [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=20250829-passierbar-losen-cd47a4b68c3d@brauner \
--to=brauner@kernel.org \
--cc=gnoack@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=viro@zeniv.linux.org.uk \
--cc=zhao.xichao@vivo.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