From: Randy Dunlap <rdunlap@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Brendan Higgins <brendanhiggins@google.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: linux-next: Tree for Apr 10 (lib/test_printf.ko)
Date: Wed, 15 Apr 2020 12:16:49 -0700 [thread overview]
Message-ID: <26e0f0dd-4ea2-14e7-fae5-81a5a1451272@infradead.org> (raw)
In-Reply-To: <20200415185545.GA1632@home.goodmis.org>
On 4/15/20 11:55 AM, Steven Rostedt wrote:
> On Tue, Apr 14, 2020 at 12:26:29PM -0700, Brendan Higgins wrote:
>> On Sat, Apr 11, 2020 at 11:22 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>> On 4/11/20 10:36 PM, Naresh Kamboju wrote:
>>>> FYI,
>>>>
>>>> Is this problem related to,
>>>>
>>>> Regression reported on Linux next 5.6.0-rc4-next-20200305 on x86_64,
>>>> i386, arm and arm64. The steps to reproduce is running kselftests lib
>>>> printf.sh test case.
>>>> Which is doing modprobe operations.
>>>>
>>>> BUG: kernel NULL pointer dereference, address: 00 - ida_free+0x76/0x140
>>>>
>>>> https://lore.kernel.org/linux-kselftest/CAFd5g46Bwd8HS9-xjHLh_rB59Nfw8iAnM6aFe0QPcveewDUT6g@mail.gmail.com/T/
>>>>
>>>
>>> Looks similar. Lots of fwnode, software_node, ida stuff there.
>>
>> Sorry for the late reply, I was out.
>>
>> Yeah, I am pretty sure it is the same. Heikki proposed a fix that I am
>> going to try.
>
> My test suite just tripped over this bug. Is this the patch that you think
> fixes it?
>
> https://lore.kernel.org/linux-kselftest/20200414081513.GD2828150@kuha.fi.intel.com
Yes, it is, but GregKH and Rafael Wysocki don't seem to like that patch
and are suggesting some changes in lib/kobject.c (only pseudocode,
no patch yet).
> I'll add it to see if I can continue my testing.
See the thread
[PATCH v1] kobject: make sure parent is not released before children
Here is Rafael's suggestion:
https://lore.kernel.org/linux-kselftest/CAJZ5v0hNemTDVa_S-FfVMbrKjM-RWYoHh88asnUvTNxZinY2cw@mail.gmail.com/
--
~Randy
next prev parent reply other threads:[~2020-04-15 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 3:27 linux-next: Tree for Apr 10 Stephen Rothwell
2020-04-10 16:35 ` linux-next: Tree for Apr 10 (lib/test_printf.ko) Randy Dunlap
2020-04-10 18:11 ` Linus Torvalds
2020-04-10 18:29 ` Randy Dunlap
2020-04-10 19:05 ` Linus Torvalds
2020-04-10 19:41 ` Randy Dunlap
2020-04-10 20:13 ` Linus Torvalds
2020-04-12 5:36 ` Naresh Kamboju
2020-04-12 6:22 ` Randy Dunlap
2020-04-14 19:26 ` Brendan Higgins
2020-04-15 18:55 ` Steven Rostedt
2020-04-15 19:16 ` Randy Dunlap [this message]
2020-04-15 19:28 ` Steven Rostedt
2020-04-12 3:46 ` linux-next: Tree for Apr 10 (warning: objtool: ___bpf_prog_run()) Randy Dunlap
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=26e0f0dd-4ea2-14e7-fae5-81a5a1451272@infradead.org \
--to=rdunlap@infradead.org \
--cc=brendanhiggins@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=naresh.kamboju@linaro.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).