From: Greg KH <gregkh@linuxfoundation.org>
To: Ronnie Sahlberg <rsahlberg@ciq.com>
Cc: stable@vger.kernel.org
Subject: Re: Candidates for stable v6.9..v6.10-rc3 Kernel Panic
Date: Wed, 19 Jun 2024 14:01:45 +0200 [thread overview]
Message-ID: <2024061929-panorama-roving-256b@gregkh> (raw)
In-Reply-To: <CAK4epfwEe5vuSYLvn2M2hdpy8WxRcnZ063LKCeqp1FqOU=30kQ@mail.gmail.com>
On Fri, Jun 14, 2024 at 02:13:57PM -0400, Ronnie Sahlberg wrote:
> The following is a pruned list of commits from upstream v6.9..v6.10-rc3
> that looks like genuine kernel panics.
>
> As far as I can tell these are not yet in linux-rolling-stable
>
> If there are issues with the list or things I cna improve when pruning the list
> please let me know
>
> a6736a0addd60fccc3a3
> 79f18a41dd056115d685
> 8eef5c3cea65f248c99c
> 12cda920212a49fa22d9
> b01e1c030770ff3b4fe3
> 744d197162c2070a6045
> 3f0c44c8c21cfa3bb6b7
> 0105eaabb27f31d9b8d3
> 6434e69814b159608a23
> d38e48563c1f70460503
> c8b3f38d2dae03979448
> 33afbfcc105a57215975
> 491aee894a08bc9b8bb5
> d0d1df8ba18abc57f28f
> ffbe335b8d471f79b259
> 93c1800b3799f1737598
> 3c34fb0bd4a4237592c5
> ffb9072bce200a4d0040
> 9dedabe95b49ec9b0d16
> 788e4c75f831d06fcfbb
> 642f89daa34567d02f31
> f55cd31287e5f77f226c
> 6ca445d8af0ed5950ebf
> ed281c6ab6eb8a914f06
> e8dc41afca161b988e6d
> c6a6c9694aadc4c3ab8d
> eebadafc3b14d9426fa9
> 29b4c7bb8565118e2c7e
> da0e01cc7079124cb1e8
> b66c079aabdff3954e93
> 514ca22a25265e9bef10
> 05090ae82f44570fefdd
> 3b89ec41747a6b6b8c7b
> 57787fa42f9fc12fe189
> 1af2dface5d286dd1f2f
> 81bf14519a8ca17af4f0
> 991b5e2aad870828669c
> 17b0dfa1f35bf58c17ae
Lots of false-positives in here as well :(
prev parent reply other threads:[~2024-06-19 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 18:13 Candidates for stable v6.9..v6.10-rc3 Kernel Panic Ronnie Sahlberg
2024-06-19 12:01 ` Greg KH [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=2024061929-panorama-roving-256b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=rsahlberg@ciq.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