From: Kees Cook <keescook@chromium.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: david@fromorbit.com, linux-xfs@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCHSET 0/3] xfs: ubsan fixes for 6.5-rc2
Date: Fri, 14 Jul 2023 14:11:48 -0700 [thread overview]
Message-ID: <202307141410.A83FB7167@keescook> (raw)
In-Reply-To: <168934573961.3353217.18139786322840965874.stgit@frogsfrogsfrogs>
On Fri, Jul 14, 2023 at 07:42:19AM -0700, Darrick J. Wong wrote:
> Hi all,
>
> Fix some UBSAN complaints, since apparently they don't allow flex array
> declarations with array[1] anymore.
Thanks for finding the best way to do this! Everything looks sane to me,
and the changes in sizes look correctly identified/checked.
Reviewed-by: Kees Cook <keescook@chromium.org>
-Kees
>
> If you're going to start using this mess, you probably ought to just
> pull from my git trees, which are linked below.
>
> This is an extraordinary way to destroy everything. Enjoy!
> Comments and questions are, as always, welcome.
>
> --D
>
> kernel git tree:
> https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=ubsan-fixes-6.5
> ---
> fs/xfs/libxfs/xfs_da_format.h | 75 ++++++++++++++++++++++++++++++++++++-----
> fs/xfs/libxfs/xfs_fs.h | 4 +-
> fs/xfs/xfs_ondisk.h | 5 ++-
> 3 files changed, 71 insertions(+), 13 deletions(-)
>
--
Kees Cook
prev parent reply other threads:[~2023-07-14 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 14:42 [PATCHSET 0/3] xfs: ubsan fixes for 6.5-rc2 Darrick J. Wong
2023-07-14 14:42 ` [PATCH 1/3] xfs: convert flex-array declarations in struct xfs_attrlist* Darrick J. Wong
2023-07-14 14:42 ` [PATCH 2/3] xfs: convert flex-array declarations in xfs attr leaf blocks Darrick J. Wong
2023-07-14 14:42 ` [PATCH 3/3] xfs: convert flex-array declarations in xfs attr shortform objects Darrick J. Wong
2023-07-14 21:11 ` Kees Cook [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=202307141410.A83FB7167@keescook \
--to=keescook@chromium.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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