From: Jens Axboe <[email protected]>
To: Linux regressions mailing list <[email protected]>
Cc: "[email protected]" <[email protected]>,
[email protected], LKML <[email protected]>,
"Sergey V." <[email protected]>,
Greg Kroah-Hartman <[email protected]>
Subject: Re: [regression] Bug 216932 - io_uring with libvirt cause kernel NULL pointer dereference since 6.1.5
Date: Mon, 16 Jan 2023 06:42:28 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/16/23 6:17?AM, Linux kernel regression tracking (Thorsten Leemhuis) wrote:
> Hi, this is your Linux kernel regression tracker.
>
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developer don't keep an eye on it, I decided to forward it by
> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216932 :
Looks like:
commit 6d47e0f6a535701134d950db65eb8fe1edf0b575
Author: Jens Axboe <[email protected]>
Date: Wed Jan 4 08:52:06 2023 -0700
block: don't allow splitting of a REQ_NOWAIT bio
got picked up by stable, but not the required prep patch:
commit 613b14884b8595e20b9fac4126bf627313827fbe
Author: Jens Axboe <[email protected]>
Date: Wed Jan 4 08:51:19 2023 -0700
block: handle bio_split_to_limits() NULL return
Greg/team, can you pick the latter too? It'll pick cleanly for
6.1-stable, not sure how far back the other patch has gone yet.
--
Jens Axboe
next prev parent reply other threads:[~2023-01-16 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 13:17 [regression] Bug 216932 - io_uring with libvirt cause kernel NULL pointer dereference since 6.1.5 Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-16 13:42 ` Jens Axboe [this message]
2023-01-16 13:54 ` Linux kernel regression tracking (#update)
2023-01-16 14:13 ` Jens Axboe
2023-01-16 14:49 ` Greg Kroah-Hartman
2023-01-16 15:44 ` Jens Axboe
2023-01-16 15:50 ` Jens Axboe
2023-02-03 9:17 ` Greg Kroah-Hartman
2023-02-03 14:25 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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