[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120923152137.GC2994@moon>
Date: Sun, 23 Sep 2012 19:21:37 +0400
From: Cyrill Gorcunov <gorcunov@...nvz.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
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 Sun, Sep 23, 2012 at 07:46:24AM -0700, H. Peter Anvin wrote:
> >changed right after that operation). Maybe I should put everything to
> >procfs, or stick back with ioctl calls?
>
> The problem as I see it is that you don't know if your process is
> the lock holder.
Wait, Peter, this lock is set via ioctl call on the fd obtained from
open(ptmx) call, so i fail to see how one can setup such lock without
having fd on the hands. When we do checkpoint the processes we expect
the user passes us the pid of process which is the leader not some
subtree (we can deal with process subtrees too but it is not
encouraged ;)
--
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/
Powered by blists - more mailing lists