linux-kernel - Re: Build broken on s390 and ia64 [was: Linux 2.6.32.58]

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:	Fri, 09 Mar 2012 09:23:32 +0100
From:	Jiri Slaby <jslaby@...e.cz>
To:	Willy Tarreau <w@....eu>
CC:	Ben Hutchings <ben@...adent.org.uk>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
	Tony Luck <tony.luck@...el.com>,
	Jiri Slaby <jirislaby@...il.com>, raven@...maw.net
Subject: Re: Build broken on s390 and ia64 [was: Linux 2.6.32.58]

On 03/09/2012 07:57 AM, Willy Tarreau wrote:
> Thanks but now I have a doubt, maybe Jiri and Tony can help. In the
> commit above, Tony says that CONFIG_COMPAT has been broken for a long
> time (2008) and nobody apparently uses it. Still, Jiri got a build
> failure because he used CONFIG_COMPAT. So either there are some valid
> uses and we should not remove the feature that late in a stable branch,
> or Jiri only encountered it upon a make allyesconfig then it might
> be safe to remove it.

It's a SLE11-SP1 that is using the kernel and has COMPAT on ia64
enabled. I don't know if it is broken or if we provide support for that.

If you are sure COMPAT is broken on ia64 even in 2.6.32, feel free to
ban COMPAT completely.

thanks,
-- 
js
suse labs
--
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/