mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: andrew@lunn.ch, linux-kernel@vger.kernel.org, andrew.lunn@ascom.ch
Subject: Re: 2.6-test4 Traditional pty and devfs
Date: Tue, 2 Sep 2003 18:42:36 +0100	[thread overview]
Message-ID: <20030902184236.A14715@infradead.org> (raw)
In-Reply-To: <20030902102141.44dc7297.akpm@osdl.org>; from akpm@osdl.org on Tue, Sep 02, 2003 at 10:21:41AM -0700

On Tue, Sep 02, 2003 at 10:21:41AM -0700, Andrew Morton wrote:
> > > Both patches suffer from a problem. The slave is always only RW
> > > root. 2.4 sets the owner of the slave to that of the process opening
> > > the master. I cannot see a way to make this happen with 2.6-test. 
> > 
> > Well, that's why we have UNIX98 ptys.  My preferred fix for this
> > issue would be to just axe traditional ptys, although this would probably
> > make it us incompatible with libc5.
> 
> Unless we made an explicit decision to kill off old-style ptys (and we did
> not do that), they should continue to work as in 2.4, yes?

They work as they do in 2.4 and 2.6 (and any previous kernel) without
devfs, remember the pt_chown pain?

There's no point in emulating half of the UNIX98 pty semantics
in devfs when we have UNIX98 ptys that do it right anyway.

> IOW: we broke it.  Have you any theory as to which change caused this?

That's the magic use uid/gid of the process calling devfs_Register flag
I killed.  With a big HEADSUP and explanation on lkml..

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
On Tue, Sep 02, 2003 at 10:21:41AM -0700, Andrew Morton wrote:
> > > Both patches suffer from a problem. The slave is always only RW
> > > root. 2.4 sets the owner of the slave to that of the process opening
> > > the master. I cannot see a way to make this happen with 2.6-test. 
> > 
> > Well, that's why we have UNIX98 ptys.  My preferred fix for this
> > issue would be to just axe traditional ptys, although this would probably
> > make it us incompatible with libc5.
> 
> Unless we made an explicit decision to kill off old-style ptys (and we did
> not do that), they should continue to work as in 2.4, yes?

They work as they do in 2.4 and 2.6 (and any previous kernel) without
devfs, remember the pt_chown pain?

There's no point in emulating half of the UNIX98 pty semantics
in devfs when we have UNIX98 ptys that do it right anyway.

> IOW: we broke it.  Have you any theory as to which change caused this?

That's the magic use uid/gid of the process calling devfs_Register flag
I killed.  With a big HEADSUP and explanation on lkml..


  reply	other threads:[~2003-09-02 18:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 10:42 Andrew Lunn
2003-09-02 14:08 ` Christoph Hellwig
2003-09-02 17:21   ` Andrew Morton
2003-09-02 17:42     ` Christoph Hellwig [this message]
2003-09-02 17:43       ` Andrew Morton
2003-09-02 18:02         ` Christoph Hellwig
2003-09-02 18:16           ` Andrew Lunn
2003-09-02 18:29             ` Christoph Hellwig
2003-09-02 18:35               ` Andrew Lunn
2003-09-02 18:08   ` Andrew Lunn
2003-09-03  2:52 Albert Cahalan
2003-09-03  6:35 ` 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=20030902184236.A14715@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=andrew.lunn@ascom.ch \
    --cc=andrew@lunn.ch \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®