linux-kernel - Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2601 trace_hardirqs_on

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]

Message-ID: <20160131131506.4aad01b5@canb.auug.org.au>
Date:	Sun, 31 Jan 2016 13:15:06 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jesper Dangaard Brouer <brouer@...hat.com>
Cc:	Valdis.Kletnieks@...edu,
	kernel test robot <fengguang.wu@...el.com>, LKP <lkp@...org>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Andrew Morton <akpm@...ux-foundation.org>, wfg@...ux.intel.com,
	Christoph Lameter <cl@...ux.com>, Tejun Heo <tj@...nel.org>,
	Joonsoo Kim <iamjoonsoo.kim@....com>
Subject: Re: [slab] a1fd55538c: WARNING: CPU: 0 PID: 0 at
 kernel/locking/lockdep.c:2601 trace_hardirqs_on_caller()

Hi Jesper,

On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer <brouer@...hat.com> wrote:
>
> Let me know, if the linux-next tree need's an explicit fix?

It would be a good idea if you could send a fix against linux-next to
me as Andrew is currently travelling.

-- 
Cheers,
Stephen Rothwell