linux-kernel - Re: How to lock current->signal->tty

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: <44D9C670.5060609@sgi.com>
Date:	Wed, 09 Aug 2006 13:26:40 +0200
From:	Jes Sorensen <jes@....com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	"Luck, Tony" <tony.luck@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: How to lock current->signal->tty

Alan Cox wrote:
> Ar Mer, 2006-08-09 am 04:09 -0400, ysgrifennodd Jes Sorensen:
>> Personally I don't like the current approach. However, I believe the
>> philosophy behind it is that users rarely look in dmesg and they
>> should be notified (and beaten with a stick) when their badly written
>> app spawns unaligned accesses which end up being emulated by the
>> kernel.
> 
> The users won't seem the anyway, they are hidden behind the GUI.

Regularly see complaints from users in the HPC space over this .....
clearly it's the kernel thats broken, not their buggy code.

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