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] [day] [month] [year] [list]
Date:	Sat, 7 Nov 2009 22:14:36 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	Arnd Bergmann <arnd@...db.de>, Pavel Machek <pavel@....cz>,
	LKML <linux-kernel@...r.kernel.org>,
	Thierry Vignaud <tvignaud@...driva.com>,
	bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bug 14537] New: missing compat_ioctl on x86_64

On Sat, 7 Nov 2009, Rafael J. Wysocki wrote:

> On Saturday 07 November 2009, Arnd Bergmann wrote:
> > On Saturday 07 November 2009, Rafael J. Wysocki wrote:
> > > > Actually... it would be nice to fix that one day, if someone submitted
> > > > nice patch... :-).   
> > > 
> > > It must be fixed in s2disk first, but that would probably require us to drop
> > > support for older kernels.  Which is not unthinkable, but might hurt some
> > > users.
> > 
> > You don't need to drop support for older kernels if s2disk simply tries the
> > new interface first and falls back to the current one if that fails.
> 
> Compat ioctls support is not possible with the old interface.

That does not matter.

If you create a new interface which is 32/64bit safe and keep the old
interface around for compability reasons then a new user space will
try the new interface first and if that is not available due to older
kernel version it uses the old interface. If old user space talks to a
newer kernel it will use the old interface with its current
limitations. Over time you can phase out the old interface in the
kernel.

Thanks,

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