From: Kees Cook <kees@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, stable@vger.kernel.org,
ryabinin.a.a@gmail.com, elver@google.com, andreyknvl@gmail.com,
smostafa@google.com
Subject: Re: + lib-test_ubsanc-fix-panic-from-test_ubsan_out_of_bounds.patch added to mm-hotfixes-unstable branch
Date: Tue, 15 Apr 2025 10:09:24 -0700 [thread overview]
Message-ID: <202504151009.C1C7343CC@keescook> (raw)
In-Reply-To: <20250415001108.79E0BC4CEE2@smtp.kernel.org>
On Mon, Apr 14, 2025 at 05:11:07PM -0700, Andrew Morton wrote:
>
> The patch titled
> Subject: lib/test_ubsan.c: fix panic from test_ubsan_out_of_bounds
> has been added to the -mm mm-hotfixes-unstable branch. Its filename is
> lib-test_ubsanc-fix-panic-from-test_ubsan_out_of_bounds.patch
Let's get the v2 instead of this version...
--
Kees Cook
prev parent reply other threads:[~2025-04-15 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 0:11 + lib-test_ubsanc-fix-panic-from-test_ubsan_out_of_bounds.patch added to mm-hotfixes-unstable branch Andrew Morton
2025-04-15 17:09 ` 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=202504151009.C1C7343CC@keescook \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=elver@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=smostafa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox