linux-kernel - Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache

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: <20140730122135.GE28613@hansolo.jdub.homelinux.org>
Date:	Wed, 30 Jul 2014 08:21:35 -0400
From:	Josh Boyer <jwboyer@...oraproject.org>
To:	Christoph Hellwig <hch@....de>
Cc:	James Bottomley <James.Bottomley@...senPartnership.com>,
	Vladimir Davydov <vdavydov@...allels.com>,
	linux-scsi@...r.kernel.org,
	Mailing-List fedora-kernel <kernel@...ts.fedoraproject.org>,
	poma <pomidorabelisima@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Paolo Bonzini <pbonzini@...hat.com>,
	Christoph Lameter <cl@...ux.com>
Subject: Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69
 kmem_cache_create+0x1a9/0x330()

On Tue, Jul 29, 2014 at 02:26:11PM +0200, Christoph Hellwig wrote:
> On Mon, Jul 28, 2014 at 11:49:22AM +0400, James Bottomley wrote:
> > That needs to be
> > 
> > From: James Bottomley <JBottomley@...allels.com>
> > 
> > As well.  I do list handling on hansenpartnership.com to minimise
> > exchange wreckage on mailinglists, but I should acknowledge Parallels as
> > supporting the work I do.
> 
> Thanks, I've update the author, added a Cc to ћtable and pushed it out to
> the core-for-3.17 branch.

This fixes a bug in the 3.16 kernel.  Why wouldn't it be sent to Linus
for inclusion in the final release there?

josh
--
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/