From: Greg KH <gregkh@linuxfoundation.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: sashal@kernel.org, dvyukov@google.com, stable@vger.kernel.org,
syzkaller@googlegroups.com
Subject: Re: Missing fix backports detected by syzbot
Date: Thu, 5 Sep 2024 10:04:22 +0200 [thread overview]
Message-ID: <2024090538-closure-mom-49c0@gregkh> (raw)
In-Reply-To: <20240904102455.911642-1-nogikh@google.com>
On Wed, Sep 04, 2024 at 12:24:55PM +0200, Aleksandr Nogikh wrote:
> Hi Greg, Sasha,
>
> A number of commits were identified[1] by syzbot as non-backported
> fixes for the fuzzer-detected findings in various Linux LTS trees.
>
> [1] https://syzkaller.appspot.com/upstream/backports
>
> Please consider backporting the following commits to LTS v6.1:
> 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 "Bluetooth: SCO: Fix possible circular locking dependency on sco_connect_cfm"
> (fixes 9a8ec9e) 3dcaa192ac2159193bc6ab57bc5369dcb84edd8e "Bluetooth: SCO: fix sco_conn related locking and validity issues"
> 3f5424790d4377839093b68c12b130077a4e4510 "ext4: fix inode tree inconsistency caused by ENOMEM"
> 7b0151caf73a656b75b550e361648430233455a0 "KVM: x86: Remove WARN sanity check on hypervisor timer vs. UNINITIALIZED vCPU"
Note, for kvm, and for:
> 4b827b3f305d1fcf837265f1e12acc22ee84327c "xfs: remove WARN when dquot cache insertion fails"
xfs patches, we need explicit approval from the subsystem maintainers to
take them into stable as they were not marked for such.
Please work with them to get those patches merged if you wish to see
them in stable trees.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-05 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:24 Missing fix backports detected by syzbot Aleksandr Nogikh
2024-09-04 10:26 ` Greg KH
2024-09-05 8:04 ` Greg KH [this message]
2024-09-05 8:12 ` Greg KH
2024-09-06 14:55 ` Aleksandr Nogikh
2024-09-06 17:23 ` 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=2024090538-closure-mom-49c0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dvyukov@google.com \
--cc=nogikh@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzkaller@googlegroups.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