From: Jes Sorensen <jes@sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Luck, Tony" <tony.luck@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: How to lock current->signal->tty
Date: Wed, 09 Aug 2006 13:26:40 +0200 [thread overview]
Message-ID: <44D9C670.5060609@sgi.com> (raw)
In-Reply-To: <1155120250.5729.146.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2006-08-09 11:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 15:17 How to lock current->signal->tty Alan Cox
2006-08-08 15:10 ` Arjan van de Ven
2006-08-08 15:44 ` Alan Cox
2006-08-08 16:41 ` Luck, Tony
2006-08-08 17:50 ` Alan Cox
2006-08-09 8:09 ` Jes Sorensen
2006-08-09 10:44 ` Alan Cox
2006-08-09 11:26 ` Jes Sorensen [this message]
2006-08-09 16:24 ` Luck, Tony
2006-08-09 18:10 ` Jes Sorensen
2006-08-08 22:06 ` Jan Kara
2006-08-08 17:11 ` Stephen Smalley
2006-08-08 17:43 ` Alan Cox
2006-08-08 17:44 ` Stephen Smalley
2006-08-08 18:10 ` Alan Cox
2006-08-08 20:02 ` Stephen Smalley
2006-08-13 21:34 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 4:01 Albert Cahalan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44D9C670.5060609@sgi.com \
--to=jes@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox