linux-kernel - Re: wpa supplicant/ipw3945, ESSID last char missing

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]

Message-ID: <Pine.LNX.4.64.0610041522190.3952@g5.osdl.org>
Date:	Wed, 4 Oct 2006 15:26:09 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Jean Tourrilhes <jt@....hp.com>
cc:	"John W. Linville" <linville@...driver.com>,
	Jeff Garzik <jeff@...zik.org>,
	Lee Revell <rlrevell@...-job.com>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	Norbert Preining <preining@...ic.at>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	johannes@...solutions.net
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Wed, 4 Oct 2006, Jean Tourrilhes wrote:
>
> 	Sometime breaking userspace APIs is perfectly OK, while
> sometimes it's not. You just have to make sure that Linus does not
> hear about it, I guess ;-)

I see the smiley, and I think you're trying to be funny and clever, but 
the thing is, I actually think that's _true_.

It's perfectly fine to break ABI's if nobody ever complains loudly enough 
that other developers notice.

So yes, we could actually even make it a real hard rule:

   "Breaking ABI's is fine. As long as you can hide the breakage so well 
    that nobody complains loudly enough that anybody ever notices".

The very fact that this turned into a discussion is a sign that the ABI 
breakage wasn't handled well enough. Usually, when we do something, nobody 
ever even notices.

(For an example of such a ABI breakage: I changed ptrace() to not allow 
ptracing another thread in the same thread group about a year ago, because 
it turned out that it was a serious local DoS problem. In the 12 months 
since, I think we had two people who ever actually noticed, and both of 
them actually caused some discussion about ways to perhaps unbreak it.)

			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/