linux-kernel - Re: [GIT]: Sparc

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: <20080428062935.GA13876@infradead.org>
Date:	Mon, 28 Apr 2008 02:29:35 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	David Miller <davem@...emloft.net>
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT]: Sparc

On Sun, Apr 27, 2008 at 05:01:39PM -0700, David Miller wrote:
> 
> Several fixes and cleanups:
> 
> 1) Remove SunOS signal frame support, that Linux used for like
>    a month some 12 years ago :-)  I added an assertion that checks
>    to make sure 32-bit processes request the newer style signal
>    frames, which I doubt will ever trigger since Jakub Jelinek
>    and myself are probably the only two people on the planet who
>    ever had such Linux binaries on their system :-)

Is a WARN_ON the right check for user-triggerable behaviour?  I think
a normal rate-limited printk with a descriptive text would be better.

>    Getting rid of the EBUS layer is much hardware, and will require

					  harder? :)

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