From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Sami Korkalainen <sami.korkalainen@proton.me>
Cc: Andrew Lunn <andrew@lunn.ch>,
Linux Stable <stable@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Brad Spengler <spender@grsecurity.net>,
regressions@leemhuis.info
Subject: Re: [REGRESSION][BISECTED] Boot stall from merge tag 'net-next-6.2'
Date: Thu, 22 Jun 2023 15:40:15 +0200 [thread overview]
Message-ID: <CAHmME9obXuj3qM8RkVqoKeU41--HqzMF-KEdNcepFWKCMAXCfQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=who5-p3QKFnio2nA9b4yf0qrV-KZ8bJa7m80ouJbvOfoA@mail.gmail.com>
On Wed, Jun 21, 2023 at 9:51 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> Now, with non-repeatable boot failures, anything is possible, and Sami
> does mention 6.1.30 as good (implying that 6.1.31 might not be - and
> that is when the backport happened).
>
> So it's certainly worth checking out, but on the face of it, that
> bisection result doesn't really support the bug being due to
> e9523a0d81899 (which came *after* e7b813b32a42).
Sami - awaiting your results.
next prev parent reply other threads:[~2023-06-22 13:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 19:17 [REGRESSION][BISECTED] Boot stall from merge tag 'net-next-6.2' Sami Korkalainen
2023-05-27 1:17 ` Bagas Sanjaya
2023-05-27 4:07 ` Sami Korkalainen
2023-06-12 14:07 ` Bagas Sanjaya
2023-06-12 19:05 ` Sami Korkalainen
2023-06-12 19:50 ` Andrew Lunn
2023-06-21 6:07 ` Sami Korkalainen
2023-06-21 8:46 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-21 17:56 ` Linus Torvalds
2023-06-21 18:08 ` Linus Torvalds
2023-06-22 18:34 ` Thorsten Leemhuis
2023-06-21 17:57 ` Jason A. Donenfeld
2023-06-23 13:55 ` Ard Biesheuvel
2023-06-23 17:29 ` Linus Torvalds
2023-06-23 20:30 ` Jason A. Donenfeld
2023-06-23 21:52 ` Linus Torvalds
2023-06-23 22:55 ` Ard Biesheuvel
2023-06-23 23:02 ` Linus Torvalds
2023-06-25 15:36 ` David Laight
2023-06-25 14:40 ` Jason A. Donenfeld
2023-06-23 18:20 ` Sami Korkalainen
2023-06-23 18:38 ` Ard Biesheuvel
2023-06-23 19:01 ` Linus Torvalds
2023-06-21 18:49 ` Jason A. Donenfeld
2023-06-21 19:51 ` Linus Torvalds
2023-06-22 13:40 ` Jason A. Donenfeld [this message]
2023-06-22 19:25 ` Sami Korkalainen
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=CAHmME9obXuj3qM8RkVqoKeU41--HqzMF-KEdNcepFWKCMAXCfQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=andrew@lunn.ch \
--cc=bagasdotme@gmail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sami.korkalainen@proton.me \
--cc=spender@grsecurity.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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.