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: <1157886908.22571.11.camel@localhost.localdomain>
Date:	Sun, 10 Sep 2006 12:15:08 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH RFC]: New termios take 2

Ar Sul, 2006-09-10 am 11:46 +0100, ysgrifennodd David Woodhouse:
> On Tue, 2006-09-05 at 17:14 +0100, Alan Cox wrote:
> > +
> > +#define TCGETS2                _IOR('T',0x2A, struct termios)
> > +#define TCSETS2                _IOW('T',0x2B, struct termios)
> > +#define TCSETSW2       _IOW('T',0x2C, struct termios)
> > +#define TCSETSF2       _IOW('T',0x2D, struct termios)
> 
> So existing code compiled against this will be using the new 'struct
> termios' but the old TCGETS. Should we rename the existing ioctl to 
> TCGETS_OLD, and have TCGETS be the new one?

Kernel headers are not intended for user space. In this case the struct
termios presented by glibc already differs from the termios presented by
the kernel so the problem doesn't arise at all.

Alan

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ