From: Christoph Hellwig <hch@lst.de>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: devpts multiple instances feedback
Date: Mon, 26 Jan 2009 22:55:42 +0100 [thread overview]
Message-ID: <20090126215542.GA20760@lst.de> (raw)
In-Reply-To: <20090105210940.GA31629@us.ibm.com>
On Mon, Jan 05, 2009 at 01:09:40PM -0800, Sukadev Bhattiprolu wrote:
> Making the pts/ptmx node would certianly simplify the code. But we
> ended up with some of the complexity to preserve the legacy behavior.
> I believe there was some concern that the presence of a "shadow"
> ptmx node on older distros might affect rights management (eg: if
> the older distro which does not know about /dev/pts/ptmx, applied
> a security label to /dev/ptmx that label could be subverted by using
> /dev/pts/ptmx ?
>
> That was also one of the reasons for the default 000 mode on the pts/ptmx
> device node
So just make it 000 but always created it.
>
> | - the 000 mode is very weird, given how the /dev/ptmx operates
> | it doesn't really make much sense to have it different than 0666
> | unless you want to disable ptys.
> | - why does pts_sb_from_inode have to check s_magic, I can't see
> | it ever used on an inode not from the devpts filesystem
>
> If /dev/ptmx is not a symlink to pts/ptmx, we would need the s_magic
> check ? (eg: when called from devpts_new_index()). The check would
> not be needed if /dev/ptmx is always a symlink.
Ok, so it's for the /dev/ptmx node. Just make that explicit by
passing down a paramter then.
next prev parent reply other threads:[~2009-01-26 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 15:52 devpts multiple instances feedback Christoph Hellwig
2009-01-03 16:15 ` Christoph Hellwig
2009-01-26 21:53 ` Christoph Hellwig
2009-01-27 3:32 ` Sukadev Bhattiprolu
2009-01-05 21:09 ` Sukadev Bhattiprolu
2009-01-26 21:55 ` Christoph Hellwig [this message]
2009-01-26 21:58 ` Alan Cox
2009-02-01 16:29 ` Christoph Hellwig
2009-02-01 16:41 ` Alan Cox
2009-01-26 21:58 ` H. Peter Anvin
2009-02-01 16:31 ` Christoph Hellwig
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=20090126215542.GA20760@lst.de \
--to=hch@lst.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.