linux-kernel - Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer

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: <20071214175910.GA27078@elte.hu>
Date:	Fri, 14 Dec 2007 18:59:10 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Michael Buesch <mb@...sch.de>
Cc:	Ray Lee <ray-lk@...rabbit.org>, stefano.brivio@...imi.it,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"John W. Linville" <linville@...driver.com>,
	Daniel Walker <dwalker@...sta.com>,
	matthias.kaehlcke@...il.com, linux-kernel@...r.kernel.org,
	mbuesch@...enet.de, linux@...mer.net, kjwinchester@...il.com,
	jonathan@...masters.org, akpm@...ux-foundation.org,
	bcm43xx-dev@...ts.berlios.de
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore
	to mutex

* Michael Buesch <mb@...sch.de> wrote:

> In my opinion this all is the work of the distributions and not the 
> work of the kernel developers. Distributions have to make sure that 
> everything works after a kernel update. [...]

actually, not. The the task of kernel developers is to KEEP OLD 
DISTRIBUTIONS WORKING WITH NEW DRIVERS. Or the "old" driver stays around 
until eternity, because the new one is just BROKEN.

Take a look at CONFIG_COMPAT_VDSO for example - one single version of 
glibc was released in a distro that depended on a kernel vDSO bug. So 
we'll keep that aspect of the vDSO perhaps forever. Simple as that. 
Stuff must just work. Whatever it takes. Best is if you add in new stuff 
without the user noticing _ANYTHING_ but that the kernel version bumped. 
If the maintainers of the other 7 million lines of kernel code can get 
this right then the wireless code should be able to do it too. Ok?

all this "distributors will have to sort out the mess" talk is nonsense, 
and i really hope you do not truly believe in that crap. If your 
attitude is prevalent in the wireless development community then it's in 
worse shape than i thought :-(

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