From: Kevin Berry <kpberry@google.com>
To: stable@vger.kernel.org
Cc: ovt@google.com, Kevin Berry <kpberry@google.com>
Subject: [PATCH 0/1] xfs: fix log recovery buffer allocation for the
Date: Sat, 10 Aug 2024 01:16:45 +0000 [thread overview]
Message-ID: <20240810011646.3746457-1-kpberry@google.com> (raw)
Hi folks, in order to fix CVE-2024-39472 in kernels 5.15, 6.1, and 6.6,
I have adapted the mainline patch 45cf976008dd (xfs: fix log recovery
buffer allocation for the legacy h_size fixup) to resolve conflicts
with those kernels. Specifically, the mainline patch uses kvfree, but
the amended patch uses kmem_free since kmem_free was used in xfs until
patch 49292576136f (xfs: convert kmem_free() for kvmalloc users to
kvfree()).
I tested the patch by applying it to the above kernels and recompiling
them. I also ran xfstests on the 6.6.43 kernel with the patch applied.
In my initial xfstests run, all xfs and generic tests passed except for
generic/082, generic/269, generic/627, and xfs/155, but those tests all
passed on a second run. I'm assuming those initial failures were
unrelated to this patch, unless someone more familiar with those tests
thinks otherwise.
I'd be more than happy to do any more verification or tests if they're
required. Thanks!
Christoph Hellwig (1):
xfs: fix log recovery buffer allocation for the legacy h_size fixup
fs/xfs/xfs_log_recover.c | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
base-commit: 58b0425ff5df680d0b67f64ae1f3f1ebdf1c4de9
--
2.46.0.76.ge559c4bf1a-goog
next reply other threads:[~2024-08-10 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 1:16 Kevin Berry [this message]
2024-08-10 1:16 ` [PATCH 1/1] xfs: fix log recovery buffer allocation for the legacy h_size fixup Kevin Berry
2024-08-12 14:41 ` [PATCH 0/1] xfs: fix log recovery buffer allocation for the Greg KH
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=20240810011646.3746457-1-kpberry@google.com \
--to=kpberry@google.com \
--cc=ovt@google.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.