From: Kees Cook <keescook@chromium.org>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: Guenter Roeck <linux@roeck-us.net>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux LLVM <llvm@lists.linux.dev>,
linux-kbuild@vger.kernel.org,
Linux Regressions <regressions@lists.linux.dev>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-hardening@vger.kernel.org
Subject: Re: [CRASH][BISECTED] 6.4.1 crash in boot
Date: Mon, 3 Jul 2023 16:09:27 -0700 [thread overview]
Message-ID: <202307031606.3FD9D0D@keescook> (raw)
In-Reply-To: <202307031149.823F9A3@keescook>
On Mon, Jul 03, 2023 at 12:03:23PM -0700, Kees Cook wrote:
> Cool. xhci-hub is in your backtrace, and the above patch was made for
> something very similar (though, again, I don't see why you're getting a
> _crash_, it should _warn_ and continue normally). And, actually, also
> include this patch:
> https://lore.kernel.org/lkml/20230614181307.gonna.256-kees@kernel.org/
This is now in Linus's tree:
09b69dd4378b ("usb: ch9: Replace 1-element array with flexible array")
Please also still try with the first patch I mentioned, which is very similar:
https://lore.kernel.org/lkml/20230629190900.never.787-kees@kernel.org/
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-07-03 23:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 16:36 [CRASH][BISECTED] 6.4.1 crash in boot Mirsad Goran Todorovac
2023-07-03 1:44 ` Bagas Sanjaya
2023-07-03 3:20 ` Kees Cook
2023-07-03 3:26 ` Guenter Roeck
2023-07-03 3:53 ` Mirsad Goran Todorovac
2023-07-03 4:30 ` Kees Cook
2023-07-03 4:38 ` Guenter Roeck
2023-07-03 4:53 ` Kees Cook
2023-07-03 4:50 ` Mirsad Goran Todorovac
2023-07-03 3:58 ` Guenter Roeck
2023-07-03 5:18 ` Mirsad Goran Todorovac
2023-07-03 5:18 ` Mirsad Goran Todorovac
2023-07-03 5:41 ` Kees Cook
2023-07-03 7:03 ` Mirsad Goran Todorovac
2023-07-03 19:03 ` Kees Cook
2023-07-03 23:09 ` Kees Cook [this message]
2023-07-04 17:20 ` Mirsad Todorovac
2023-07-04 21:36 ` Kees Cook
2023-07-04 23:15 ` Mirsad Todorovac
2023-07-05 2:09 ` Kees Cook
2023-07-05 5:18 ` Mirsad Todorovac
2023-07-05 15:16 ` CONFIG_UBSAN_TRAP #UD error message on x86 [was: Re: [CRASH][BISECTED] 6.4.1 crash in boot] Jann Horn
2023-07-05 21:08 ` Kees Cook
2023-07-05 21:31 ` Peter Zijlstra
2023-07-05 21:54 ` Kees Cook
2023-07-06 5:02 ` [CRASH][BISECTED] 6.4.1 crash in boot Mirsad Todorovac
2023-07-03 3:40 ` Mirsad Goran Todorovac
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=202307031606.3FD9D0D@keescook \
--to=keescook@chromium.org \
--cc=bagasdotme@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=regressions@lists.linux.dev \
/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.