linux-kernel - Re: [RFC PATCH 0/4] Add support for LZ4-compressed kernels

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:	Thu, 31 Jan 2013 21:28:30 -0500 (EST)
From:	Nicolas Pitre <nico@...xnic.net>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Michal Marek <mmarek@...e.cz>, hyojun.im@....com,
	raphael.andy.lee@...il.com, linux-kbuild@...r.kernel.org,
	gunho.lee@....com, namhyung.kim@....com, x86@...nel.org,
	minchan.kim@....com, linux-kernel@...r.kernel.org,
	Josh Triplett <josh@...htriplett.org>,
	Nitin Gupta <nitingupta910@...il.com>,
	Richard Purdie <rpurdie@...nedhand.com>,
	Ingo Molnar <mingo@...hat.com>,
	Joe Millenbach <jmillenbach@...il.com>, chan.jeong@....com,
	Kyungsik Lee <kyungsik.lee@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Albin Tonnerre <albin.tonnerre@...e-electrons.com>,
	CE Linux Developers List <celinux-dev@...ts.celinuxforum.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 0/4] Add support for LZ4-compressed kernels

On Thu, 31 Jan 2013, H. Peter Anvin wrote:

> On 01/31/2013 02:16 PM, Nicolas Pitre wrote:
> >>
> >> Some utterly weird things like the Xen domain builder do that, because
> >> they have to.  That is why we explicitly document that the payload is
> >> ELF and how to access it in the bzImage spec.
> > 
> > Are you kidding?
> > 
> > And what format do they expect?
> > 
> 
> I think they can be fairly flexible.  Obviously gzip is always
> supported.  I don't know the details.
> 
> > If people are doing weird things with formats we're about to remove then 
> > it's their fault if they didn't make upstream developers aware of it.  
> > And if the reason they didn't tell anyone is because it is too nasty for 
> > public confession then they simply deserve to be broken and come up with 
> > a more sustainable solution.
> 
> Well, it is too nasty for public confession, but it's called
> "paravirtualization".

The fact that you are aware of it means we're not going to break them.  

But my point is that we must not be held back just in case someone out 
there might have painted himself in a corner without telling anyone.


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