Re: wpa supplicant/ipw3945, ESSID last char missing

[Jean Tourrilhes <jt@hpl.hp.com>]

On Tue, Oct 03, 2006 at 02:59:16PM -0700, Linus Torvalds wrote:
> 
> 
> On Tue, 3 Oct 2006, John W. Linville wrote:
> >
> > I.E.  With "WE-21 aware" tools already in the wild, it isn't now clear
> > to me how WE can evolve any further than WE-20.
> 
> Well, if you get a WE-22 out soon enough, the situation will be one where 
> people who are fast at updating will have a fixed version quickly, and the 
> ones that aren't quick at updating will never have even seen the broken 
> case.

	Linus,

	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.
	I personally thought that I went beyond the usual practice by
waiting 6 months, auditing all userspace and making sure the bits had
propagated to distro. And let's not forget that the tools warn users
about API mismatch.
	If you feel we need 1 more month, that's perfectly ok with all
of us. If your target is that some specific distros ship with
compatible userspace, I can personally monitor that and report. You
may want to be a bit more explicit in your standards, that would help
all of us doing a better job.

	Have fun...

	Jean