mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, Ken Werner <ken.werner@web.de>,
	Andi Kleen <andi@firstfloor.org>,
	stable@kernel.org
Subject: Re: [stable] cpumask: fix compat getaffinity
Date: Tue, 11 May 2010 14:36:04 -0700	[thread overview]
Message-ID: <20100511213604.GA27050@kroah.com> (raw)
In-Reply-To: <201005112013.56392.arnd@arndb.de>

On Tue, May 11, 2010 at 08:13:55PM +0200, Arnd Bergmann wrote:
> On Tuesday 11 May 2010 17:20:02 Greg KH wrote:
> > > AFAIK, -stable is mainly used for distro and they have many and many
> > > packages. we can't assume no app read /sys files directly.
> > > IOW, To change /sys printing format is a bit risky change. frequently
> > > compatibility breaking natually break code stability.
> > 
> > Ah, the sysfs user/kernel API is what you are referring to here, right?
> > If so, remember, any changes need to be documented in Documentation/API
> > :)
> > And as for distros using -stable for their releases, that's fine, they
> > well know the risks/benefits for that and handle changes on their own.
> 
> Would it make sense to use my initial patch for -stable, which reverts
> the ABI back to before the change that caused the problem, but apply
> the correct fix (changing the ABI throughout) for future releases?

I do not know, as I really don't know what the issue is here.

I trust that you, and the others, can come up with a fix for mainline
properly, and if it applies to the stable tree, feel free to forward it
to stable@kernel.org for submission then.

thanks,

greg k-h

  reply	other threads:[~2010-05-11 21:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 12:45 Arnd Bergmann
2010-05-08  8:30 ` Rusty Russell
2010-05-08  9:11   ` Arnd Bergmann
2010-05-10 23:43     ` Rusty Russell
2010-05-11  1:47       ` KOSAKI Motohiro
2010-05-11  3:13         ` [stable] " Greg KH
2010-05-11  5:51           ` Rusty Russell
2010-05-11  6:25             ` KOSAKI Motohiro
2010-05-11  6:20           ` KOSAKI Motohiro
2010-05-11 15:20             ` Greg KH
2010-05-11 18:13               ` Arnd Bergmann
2010-05-11 21:36                 ` Greg KH [this message]
2010-05-12  8:30           ` Milton Miller
2010-05-14 12:39             ` Rusty Russell
2010-05-17  6:04               ` KOSAKI Motohiro
2010-05-17 18:58                 ` Arnd Bergmann
2010-05-18  0:57                 ` Rusty Russell
2010-12-14 16:59                 ` Josh Hunt
2010-12-15 14:40                   ` Arnd Bergmann
2010-06-22 23:30             ` Rusty Russell
2010-05-11  9:05       ` Arnd Bergmann
2010-05-12  0:52         ` KOSAKI Motohiro

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=20100511213604.GA27050@kroah.com \
    --to=greg@kroah.com \
    --cc=andi@firstfloor.org \
    --cc=arnd@arndb.de \
    --cc=ken.werner@web.de \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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

Powered by JetHome