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: <1155120250.5729.146.camel@localhost.localdomain>
Date:	Wed, 09 Aug 2006 11:44:10 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Jes Sorensen <jes@....com>
Cc:	"Luck, Tony" <tony.luck@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: How to lock current->signal->tty

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.

> These messages are normally caused by userland code, so kprobes
> probably wont do much good :)

Jes, read up on kprobes a little if you think its of no use in these
kind of situations. A systemtap script to count/measure alignment fault
rates and see who is causing the load isn't very hard to write.

Alan

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