linux-kernel - RE: mmotm 2011-02-10-16-26 uploaded

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:	Fri, 11 Feb 2011 14:09:03 -0800 (PST)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	Valdis.Kletnieks@...edu, akpm@...ux-foundation.org
Cc:	mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
	Nitin Gupta <ngupta@...are.org>
Subject: RE: mmotm 2011-02-10-16-26 uploaded

> From: Valdis.Kletnieks@...edu [mailto:Valdis.Kletnieks@...edu]
> Sent: Friday, February 11, 2011 2:53 PM
> To: akpm@...ux-foundation.org; Dan Magenheimer
> Cc: mm-commits@...r.kernel.org; linux-kernel@...r.kernel.org; linux-
> mm@...ck.org; linux-fsdevel@...r.kernel.org
> Subject: Re: mmotm 2011-02-10-16-26 uploaded
> 
> On Thu, 10 Feb 2011 16:26:36 PST, akpm@...ux-foundation.org said:
> > The mm-of-the-moment snapshot 2011-02-10-16-26 has been uploaded to
> >
> >    http://userweb.kernel.org/~akpm/mmotm/
> 
> CONFIG_ZCACHE=m dies a horrid death:

Thanks Valdis.  A fix for this has already been posted by
Nitin Gupta and Randy Dunlap here:

https://lkml.org/lkml/2011/2/10/383 

Another patch for a zcache memory leak has been posted here:

https://lkml.org/lkml/2011/2/10/306 

I'm sorry that multiple people have run into this in
multiple trees.
I have to admit I am a bit baffled as to what the proper
tree flow is for bug fixes like this, but would be happy
to "follow the process" if I am told what it is or if
someone can point me to a document describing it.

(Clearly making sure there are no bugs at all in a
submission is the best way to go, but I'm afraid
I can't claim to be perfect :-)

Thanks,
Dan

P.S. I suppose there isn't really a good reason for
CONFIG_ZCACHE to be tri-state as it really makes
no sense as a module because, if CONFIG_CLEANCACHE
is enabled, it will always get loaded.
--
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/