linux-kernel - Re: [LKP] [mtd] 6b44d910ae7: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3547 check

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Apr 2015 20:02:23 +0200
From:	Frans Klaver <fransklaver@...il.com>
To:	Brian Norris <computersforpeace@...il.com>
Cc:	Huang Ying <ying.huang@...el.com>,
	LKML <linux-kernel@...r.kernel.org>, LKP ML <lkp@...org>
Subject: Re: [LKP] [mtd] 6b44d910ae7: WARNING: CPU: 0 PID: 0 at
 kernel/locking/lockdep.c:3547 check_flags+0xae/0x17b()

On Fri, Apr 17, 2015 at 6:31 PM, Brian Norris
<computersforpeace@...il.com> wrote:
> On Fri, Apr 17, 2015 at 04:19:52PM +0200, Frans Klaver wrote:
>> > On Thu, Apr 16, 2015 at 7:27 AM, Huang Ying <ying.huang@...el.com> wrote:
>> > I'm happy to
>> > send in a patch that restores "mtd->owner = THIS_MODULE" with these
>> > drivers, if that's preferred.
>>
>> Long story short, I should fix it.
>>
>> Brian, do you prefer a rework of the series or a patch fixing it?
>
> I don't have the time to handle much at the moment, so I've just removed
> your series from my +master branch. It won't go in my 4.1-rc1 pull
> request and will likely be delayed to 4.2. Feel free to send a new
> series, with a good changelog to describe the v1->v2 delta.

That will do.

Thanks,
Frans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/