linux-kernel - Re: 2.6.20-rc6-mm1

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, 29 Jan 2007 19:26:01 -0800
From:	Martin Bligh <mbligh@...igh.org>
To:	Andrew Morton <akpm@...l.org>
Cc:	suparna@...ibm.com, linux-kernel@...r.kernel.org,
	Jens Axboe <axboe@...nel.dk>,
	"Sébastien Dugué @qubit.in.ibm.com" 
	<sebastien.dugue@...l.net>
Subject: Re: 2.6.20-rc6-mm1

Andrew Morton wrote:
> On Tue, 30 Jan 2007 08:12:31 +0530
> Suparna Bhattacharya <suparna@...ibm.com> wrote:
> 
>> On Sun, Jan 28, 2007 at 03:01:33PM -0800, Andrew Morton wrote:
>>> On Sun, 28 Jan 2007 08:56:08 -0800
>>> "Martin J. Bligh" <mbligh@...igh.org> wrote:
>>>
>>>>> - It seems that people have been busy creating the need for this.  I had to
>>>>>   apply over sixty patches to this tree to fix post-2.6.20-rc4-mm1 compilation
>>>>>   errors.  And a number of patches were dropped due to no-compile or to
>>>>>   runtime errors.  Heaven knows how many runtime bugs were added.
>>>> dbench seems to panic on xfs / cfq ?
>>> OK, I'll dump git-block.patch.  That means that the fsaio patches get
>>> temporarily dropped as well as they depend on git-block changes somewhat.
>> Would you like me to rework these back again to not depend on git-block ?
> 
> Is OK thanks, I now have a git-block minus CFQ changes, so I have restored the fsaio
> patches.

On a happy note - mm2 seems to pass testing much better ;-)

M.

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