From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Ralph Siemsen <ralph.siemsen@linaro.org>,
Kees Cook <keescook@chromium.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: at25 eeprom driver: NULL pointer dereference (bisected to af40d16042d6 ("Merge v5.15-rc5 into char-misc-next"))
Date: Thu, 27 Jan 2022 09:32:06 +0000 [thread overview]
Message-ID: <17598be4-c5f5-c9ae-ee24-652fc06f36ce@csgroup.eu> (raw)
In-Reply-To: <20220126193816.GA3763305@maple.netwinder.org>
Le 26/01/2022 à 20:38, Ralph Siemsen a écrit :
> Hi Christophe,
>
> On Wed, Jan 26, 2022 at 07:18:42PM +0000, Christophe Leroy wrote:
>> Getting below Oops on boot.
>>
>> v5.16 is OK, v5.17-rc1 has the problem
>>
>> Bisected to af40d16042d6 ("Merge v5.15-rc5 into char-misc-next"), bisect
>> log after the oops dump.
>>
>> I'm a bit puzzled to end up on a merge commit, that commit doesn't show
>> any diff with 'git show' but has a huge list of changes with 'git show
>> --stat'. I must be missing something.
>
> There is a mistake in the merge commit. The fix is here:
> https://lore.kernel.org/all/20220118182003.3385019-1-keescook@chromium.org/
>
It fixes the problem, thanks.
FWIW, you can add to that patch:
Tested-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Thanks
Christophe
next prev parent reply other threads:[~2022-01-27 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 19:18 Christophe Leroy
2022-01-26 19:38 ` Ralph Siemsen
2022-01-27 9:32 ` Christophe Leroy [this message]
2022-01-27 9:37 ` Greg Kroah-Hartman
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=17598be4-c5f5-c9ae-ee24-652fc06f36ce@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralph.siemsen@linaro.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
all inboxes | Powered by JetHome®