linux-kernel - Re: 2.6.21-rc6-mm1

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]

Date:	Tue, 24 Apr 2007 10:22:50 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"J.A. Magallón" <jamagallon@....com>"@linux-foundation.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.21-rc6-mm1

On Tue, 24 Apr 2007 15:43:21 +0200 "J.A. Magallón" <jamagallon@....com> wrote:

> On Tue, 24 Apr 2007 04:58:01 -0700, Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > On Tue, 24 Apr 2007 10:10:41 +0200 "J.A. Magallón" <jamagallon@....com> wrote:
> > 
> > > On Sun, 8 Apr 2007 14:35:59 -0700, Andrew Morton <akpm@...ux-foundation.org> wrote:
> > > 
> > > > 
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
> > > > 
> > > > 
> > > > - Lots of x86 updates
> > > > 
> > > 
> > > Has somthing related with PTY's changed in this kernel ?
> > 
> > Not as far as I know, but there were some kobject_uevent changes which
> > might have caused udev upcalls to break.  Perhaps.
> > 
> > > I have to enable legacy PTY handling in a couple boxes to get ssh working.
> > > If not, I had openpty() errors and nor sshd nor virtual terminals (aterm) were
> > > able to get a terminal.
> > 
> > I have CONFIG_PM_LEGACY unset in at least one of my test configs and it
> > works OK here.
> > 
> > > User space (udev) is the same in three boxes and one works and two fail.
> > > I had /dev/ptmx everywhere and /dev/pts mounted
> > > 
> > > Any idea ?
> > 
> > Nope.  Can you please check 2.6.21-rc7-mm1, see if that fixed it?  If so,
> > it might have been the kobject_uevent thing.
> > 
> 
> I will, thanks.
> 
> A couple questions (as far as udev behaviour is sooooooo distro dependent):
> - What should I have in /dev if I don't use legacy ptys ? As I understand
>   it, only /dev/ptmx and /dev/pts/*, no /dev/tty* nor /dev/pty* ?

My FC5 CONFIG_LEGACY_PTYS=n box has no /dev/ptmx, /dev/pts/*, all of
/dev/tty0 through /dev/tty63 and no /dev/pty*.

I'm not sure where all the /dev/tty*'s came from - perhaps a static udev
rule?

> - If my setup, for whatever strange reasons has /dev/tty* stored anyware
>   (/dev/.udev, links.conf...) and they get created, I supose that opening
>   /dev/tty will give a ENODEV ?

well, /dev/tty is attached to your current tty and /dev/tty2 will get you
talking to the second VT.  I can't immediately thing what /dev/tty22 is
attached to.

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