mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nathan Lynch <ntl@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	stable@kernel.org
Subject: Re: [PATCH] signalfd: fill in ssi_int for posix timers and message queues
Date: Sat, 24 Jul 2010 21:09:21 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1007242104060.1470@davide-laptop> (raw)
In-Reply-To: <20100720211018.e586c7ce.akpm@linux-foundation.org>

On Tue, 20 Jul 2010, Andrew Morton wrote:

> It's not a matter of a current application depending on current
> behaviour!  The problem is that an application written in 2018 which
> depends on the _new_ behaviour will not work on 2.6.34.
> 
> It wouldn't be the worst thing we've ever done to our long-suffering
> users, but it is a permanent cost of having screwed things up :(

While I agree it is a problem with the kernel compatibility handling, 
every time we add new features to an existing interface we end up in 
similar scenarios.
Nowadays a "require kernel >= X.Y.Z" is all but an uncommon case for 
userspace code.


- Davide


      parent reply	other threads:[~2010-07-25  4:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03  0:38 Nathan Lynch
2010-07-03 19:09 ` Davide Libenzi
2010-07-05 12:22   ` Nathan Lynch
2010-07-05 18:23     ` Davide Libenzi
2010-07-20 22:42 ` Andrew Morton
2010-07-21  3:44   ` Nathan Lynch
2010-07-21  4:10     ` Andrew Morton
2010-07-21 17:39       ` Nathan Lynch
2010-07-25  4:09       ` Davide Libenzi [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.DEB.2.00.1007242104060.1470@davide-laptop \
    --to=davidel@xmailserver.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntl@pobox.com \
    --cc=stable@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®