lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 15 Apr 2020 14:55:45 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Brendan Higgins <brendanhiggins@...gle.com>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Rasmus Villemoes <linux@...musvillemoes.dk>,
        Heikki Krogerus <heikki.krogerus@...ux.intel.com>
Subject: Re: linux-next: Tree for Apr 10 (lib/test_printf.ko)

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@...radead.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

I'll add it to see if I can continue my testing.

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ