linux-kernel - Re: RFC arch/sh/kernel/traps_64.c - unclear if/else construct (hpux compat layer)

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]

Message-ID: <1424162967.7082.7.camel@x220>
Date:	Tue, 17 Feb 2015 09:49:27 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Helge Deller <deller@....de>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	Nicholas Mc Guire <der.herr@...r.at>,
	"James E.J. Bottomley" <jejb@...isc-linux.org>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	linux-parisc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: RFC arch/sh/kernel/traps_64.c - unclear if/else construct (hpux
 compat layer)

Hi Helge,

On Mon, 2015-02-16 at 22:24 +0100, Helge Deller wrote:
> The hpux code is broken anyway.
> I'm going to remove it from the tree.

That happened in commit 04c161497716 ("parisc: hpux - Drop support for
HP-UX binaries"), which is included in today's linux-next
(next-20150217). I noticed because a script I use to check linux-next
spotted a problem with it.

That commit removed the Kconfig symbol HPUX. As a result BINFMT_SOM (see
fs/Kconfig.binfmt) can't be set anymore. I assume a patch to remove that
symbol too is also part of that series. Is that correct?

Paul Bolle

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