linux-kernel - Re: [RFC] tty: Add get- ioctls to fetch tty status

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: <50646620.4090708@zytor.com>
Date:	Thu, 27 Sep 2012 07:43:44 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Cyrill Gorcunov <gorcunov@...nvz.org>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Pavel Emelyanov <xemul@...allels.com>,
	Jiri Slaby <jslaby@...e.cz>
Subject: Re: [RFC] tty: Add get- ioctls to fetch tty status

On 09/27/2012 07:21 AM, Cyrill Gorcunov wrote:
> On Thu, Sep 27, 2012 at 07:17:49AM -0700, H. Peter Anvin wrote:
>>> While we easily can fetch termios settings and such, there are few bits which
>>> are missed to expord. So this patch provides them to user-space.
>>>
>>
>> What bothers me (and the same applies to termios) is that you have
>> NO idea if your particular process is the "owner" of that tty.  tty
>> users use out-of-band protocols, often implicit, to determine which
>> process "owns" the tty state.
>>
>> If you can't guarantee that ALL those processes are stopped and
>> checkpointed/restarted, you have a huge problem.
>
> Well, sure inside our tool before doing checkpoint we stop all
> tasks which are part of dumpee process tree. This unfortunatly
> doesn't apply to these ioctl calls. Peter, any idea how to deal
> with that?
>

Sorry, no.  I suspect you might be trying to do something that is 
impossible to do in a general fashion without application changes.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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