linux-kernel - Re: [stable] cpumask: fix compat getaffinity

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]

Date:	Tue, 11 May 2010 20:13:55 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Greg KH <greg@...ah.com>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	linux-kernel@...r.kernel.org, Ken Werner <ken.werner@....de>,
	Andi Kleen <andi@...stfloor.org>, stable@...nel.org
Subject: Re: [stable] cpumask: fix compat getaffinity

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?

	Arnd
--
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/