linux-kernel - Re: Possible stable fix for decompressor speed

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140203135912.GC5258@hercules>
Date:	Mon, 3 Feb 2014 13:59:12 +0000
From:	Luis Henriques <luis.henriques@...onical.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jon Medhurst <tixy@...aro.org>,
	Alexandre Courbot <acourbot@...dia.com>,
	stable@...r.kernel.org, linaro-kernel@...ts.linaro.org,
	linux-kernel@...r.kernel.org
Subject: Re: Possible stable fix for decompressor speed

On Tue, Jan 28, 2014 at 04:14:28PM +0000, Mark Brown wrote:
> The changes in patch 1431574a1c4c (lib/decompressors: fix "no limit"
> output buffer length) avoid doing decompression a byte at a time when
> decompressing into high physical addresses using a small, well isolated
> change.  The patch can give a very noticable improvement in kernel boot
> times on affected systems, for example with one ARM system this reduces
> the total time to boot the kernel by more than a third.
> 
> Would you consider this patch for stable?  It doesn't quite fit within
> the criteria but you've indicated in the past that such isolated and
> well supported changs can be acceptable anyway.  If it's not OK for
> stable it seems like it should be a good candidate for LTSI.

Thanks Mark, I'm queuing this for the 3.5 and the 3.11 kernels as well.

Cheers,
--
Luis
--
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/