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: <4523FE53.4030806@garzik.org>
Date:	Wed, 04 Oct 2006 14:32:51 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	jt@....hp.com
CC:	Linus Torvalds <torvalds@...l.org>,
	"John W. Linville" <linville@...driver.com>,
	Lee Revell <rlrevell@...-job.com>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	Norbert Preining <preining@...ic.at>, hostap@...oo.com,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	johannes@...solutions.net
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

Jean Tourrilhes wrote:
> 	You can't froze kernel userspace API forever. That is simply
> not workable, it will lead to stagnation and obsolescence. This is
> especially unfair because some other kernel userspace API are allow to
> change whenever their maintainers feels like.
> 
> 	Just to give you an example why we sometime need to
> change. The first two generations of 802.11 hardware were using the
> ESSID as a C-string (no NUL char), so the API was also using a
> C-string (no NUL char). New 802.11 hardware do accept NUL in the
> ESSID, therefore the API need to evolve away from C-string to offer
> this new feature to userspace. Especially that new WPA standard may
> use that in the future (cf. Jouni's e-mail).
> 
> 	In the past, kernel userspace API changes were done during the
> devel series, but we don't have this option anymore. What I would like
> people to discuss is what are the best practice to perform kernel
> userspace API changes in 2.6.X.

You can _add_ to the userspace API, because that obviously does not 
break old programs.

You just should not introduce changes which break old programs.

Binaries built in the 1990's still work under Linux, you know...

API changes require new ioctl/sub-ioctl numbers, so that new programs 
can take advantage of new capabilities while old programs continue to work.

	Jeff


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