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: <1406732699.4865.92.camel@jarvis>
Date:	Wed, 30 Jul 2014 19:04:59 +0400
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Christoph Hellwig <hch@....de>
Cc:	Josh Boyer <jwboyer@...oraproject.org>,
	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 Wed, 2014-07-30 at 16:52 +0200, Christoph Hellwig wrote:
> On Wed, Jul 30, 2014 at 08:21:35AM -0400, Josh Boyer wrote:
> > > 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?
> 
> I'm only collecting patches for scsi, but James remains formal maintainer, so
> I don't send anything to Linus.  Given that delays between me committing
> things, them getting picked up by James and finally making it to Linux-next I
> don't feel like another for-3.16 branch at this point is easily workable.

It's been remarkably current, I believe ... it's already up to date.
However, we only have 2 -next builds between now and the anticipated
3.16 release (unless Linus does another -rc) so there's not enough time
for a patch that isn't already in (although this one is).

> If James wants to cherry pick it and send it on at this time that might
> still work fine, but he seems fairly busy.

I'll pull it out and refactor the tree.

James




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