linux-kernel - Re: How to make -mm a more viable testbed (was: [PATCH] [1/12] x86: Work around mmio config space quirk on AMD)

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:	Mon, 13 Aug 2007 14:40:06 -0600
From:	Zan Lynx <zlynx@....org>
To:	Al Boldi <a1426z@...ab.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to make -mm a more viable testbed (was: [PATCH] [1/12]
	x86: Work around mmio config space quirk on AMD)

On Mon, 2007-08-13 at 08:08 +0300, Al Boldi wrote:
> Linus Torvalds wrote:
> > On Sun, 12 Aug 2007, Dave Jones wrote:
> > > 
> > > This does make me wonder, why these weren't caught in -mm ?
> > 
> > I'm worried that -mm isn't getting a lot of exposure these days. People do 
> > run it, but I wonder how many..
> 
> Well, I'm not running it because it's got too much garbage in it, which makes 
> it a pretty unrealistic testbed.  And to make matters worse, I also stay 
> away from rc's as a consequence.
> 
> To make -mm more viable, it may be advisable to restructure -mm in such a way 
> as to be a Kconfig option to mainline.  This would probably involve some 
> patch management functionality to apply experimental submissions on a 
> per-patch basis, as opposed to being a 'take it or leave it slam onto 
> mainline' patch.

I thought most people running -mm were running klive, which shou
ld tell kernel versions, uptime and other things.  I run it, anyway.

http://klive.cpushare.com/
-- 
Zan Lynx <zlynx@....org>

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)