From: Christoph Hellwig <hch@lst.de>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Brian Foster <bfoster@redhat.com>,
Dave Chinner <david@fromorbit.com>,
Sam Sun <samsun1006219@gmail.com>,
linux-xfs@vger.kernel.org
Subject: fix h_size validation v2
Date: Tue, 30 Apr 2024 06:07:54 +0200 [thread overview]
Message-ID: <20240430040757.1653768-1-hch@lst.de> (raw)
Hi all,
this series fixes the slab out of bounds founds by Sam's fuzzer,
and tightens up the h_size validation and log recovery buffer
allocation while at it.
Changes since v1:
- fix the commit description and fixes for the first patch
- drop the previously second patch to reduce the scope of the fixup as
it needs fixing, refactoring and a good test strategy
next reply other threads:[~2024-04-30 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 4:07 Christoph Hellwig [this message]
2024-04-30 4:07 ` [PATCH 1/2] xfs: fix log recovery buffer allocation for the legacy h_size fixup Christoph Hellwig
2024-04-30 4:07 ` [PATCH 2/2] xfs: clean up buffer allocation in xlog_do_recovery_pass Christoph Hellwig
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=20240430040757.1653768-1-hch@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=samsun1006219@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).