linux-kernel - Re: sysfs regression: wrong link counts

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFwZNdoAA9iPMiEp8-+ndgV+CtSZO4neSh_L+gd77k7-vg@mail.gmail.com>
Date:	Tue, 31 Jan 2012 08:45:58 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Jiri Slaby <jslaby@...e.cz>, Greg KH <greg@...ah.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	LKML <linux-kernel@...r.kernel.org>,
	systemd-devel@...ts.freedesktop.org,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: sysfs regression: wrong link counts

On Tue, Jan 31, 2012 at 4:44 AM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
>
> The sensors update with the fix is scheduled for about a week out, well
> before 3.3 ships.

That's almost certainly *not* going to help.

Guys, people don't update their user space. Some people run modern
kernels on the enterprise distros - and those can be *years* out of
date.

If people report problems, we revert things. It's that simple. It
really doesn't matter if you call it a user space bug or not - if user
space depends on what we used to do, then we continue to do it.

We can *try* the kernel change, but I can already tell you that
anybody who thinks that "sensors will be fixed by all users by the
time the kernel comes out" is likely totally full of shit. Not to
mention that it apparently *already* causes problems for people who
want to test -next, and this breaks those peoples setup, and thus
means that -next gets less testing.

Really. "It's a bug in user space" is *NOT* an excuse for breaking
things. Never was. Never is. There are (other) excuses for breaking
things, but "user space did something I didn't expect it to do, and I
consider it a bug" is absolutely not one of them.

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