All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Arnd Bergmann <arnd@arndb.de>, Pavel Machek <pavel@ucw.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	Thierry Vignaud <tvignaud@mandriva.com>,
	bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 14537] New: missing compat_ioctl on x86_64
Date: Sat, 7 Nov 2009 22:14:36 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911072211300.12138@localhost.localdomain> (raw)
In-Reply-To: <200911072210.55270.rjw@sisk.pl>

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

      parent reply	other threads:[~2009-11-07 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14537-6666@http.bugzilla.kernel.org/>
2009-11-04 11:43 ` [Bug 14537] New: missing compat_ioctl on x86_64 Thomas Gleixner
2009-11-04 15:14   ` Andi Kleen
2009-11-04 15:41     ` Andreas Schwab
2009-11-04 16:49       ` Randy Dunlap
2009-11-04 22:12   ` Rafael J. Wysocki
2009-11-07 17:20     ` Pavel Machek
2009-11-07 19:06       ` Rafael J. Wysocki
2009-11-07 19:14         ` Pavel Machek
2009-11-07 20:52         ` Arnd Bergmann
2009-11-07 21:10           ` Rafael J. Wysocki
2009-11-07 21:12             ` Arnd Bergmann
2009-11-07 21:14             ` Thomas Gleixner [this message]

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=alpine.LFD.2.00.0911072211300.12138@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=tvignaud@mandriva.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.