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: <20060809162440.GA14143@intel.com>
Date:	Wed, 9 Aug 2006 09:24:40 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Jes Sorensen <jes@....com>, linux-kernel@...r.kernel.org
Subject: Re: How to lock current->signal->tty

On Wed, Aug 09, 2006 at 11:44:10AM +0100, Alan Cox wrote:
> 
> The users won't see them anyway, they are hidden behind the GUI.

I think that the majority of IA-64 users are connected to the target
machine via ssh login, rather than a directly connected VGA screen.
So they should see the message on their pty.

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

But this does make sense ... the system administrator of a mainframe or
super-computer can (and arguably should) be monitoring resource
utilization and providing feedback to users on how to get the best
performance from their applications.

-Tony (currently at 90% rip out this message, 10% add the mutex lock/unlock).
-
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/