linux-kernel - Re: [PATCH] include: crash

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] [day] [month] [year] [list]

Message-ID: <20120104215623.GI11810@n2100.arm.linux.org.uk>
Date:	Wed, 4 Jan 2012 21:56:23 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Fabio Estevam <festevam@...il.com>, linux-kernel@...r.kernel.org,
	Fabio Estevam <fabio.estevam@...escale.com>
Subject: Re: [PATCH] include: crash_dump.h: Add elf.h header

On Wed, Jan 04, 2012 at 12:28:05PM -0800, Andrew Morton wrote:
> The patch is the right thing to do, however I'm rather concerned about
> the potential for introducing build breakage so late in 3.2.
> 
> Can we leave this unfixed in 3.2 and fix it in 3.2.1?  Or put a
> #include elf.h into arch/arm/kernel/setup.c for 3.2?

arch/arm/kernel/setup.c doesn't need either of these includes.  The
reason I didn't want to just remove the include and magic the error
away is because of the obvious fragility of the current situation,
which really needs solving.

As this is the only report of this breakage, I'm inclined to go
with your first suggestion: leave it unfixed in 3.2 and fix it in
-stable once it's been in visible for a bit.
--
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/