From: Dan Williams <dcbw@redhat.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: jt@hpl.hp.com, Andrew Morton <akpm@osdl.org>,
"John W. Linville" <linville@tuxdriver.com>,
Norbert Preining <preining@logic.at>,
Alessandro Suardi <alessandro.suardi@gmail.com>,
hostap@shmoo.com, linux-kernel@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing
Date: Mon, 02 Oct 2006 17:00:31 -0400 [thread overview]
Message-ID: <1159822831.11771.5.camel@localhost.localdomain> (raw)
In-Reply-To: <200610022147.03748.rjw@sisk.pl>
On Mon, 2006-10-02 at 21:47 +0200, Rafael J. Wysocki wrote:
> On Monday, 2 October 2006 20:55, Jean Tourrilhes wrote:
> > On Mon, Oct 02, 2006 at 11:15:37AM -0700, Andrew Morton wrote:
> > > On Mon, 02 Oct 2006 12:58:24 -0400
> > > >
> > > > You have a mismatch between your wireless-tools, your kernel, and/or
> > > > wpa_supplicant. WE-21 uses the _real_ ssid length rather than the
> > > > kludge of hacking off the last byte used previously. Please ensure that
> > > > your tools, driver, and kernel are using WE-21.
> > > > 'cat /proc/net/wireless' should tell you what your kernel is using.
> > > > Getting the driver WE is a bit harder and you may have to look at the
> > > > source.
> > >
> > > Jean, John: the amount of trouble which this change is causing is quite
> > > high considering that we're not even at -rc1 yet. It's going to get worse.
> >
> > We have to split between the different issues we have seen.
> > Tools issue (the wpa_supplicant problem). -> those can only be
> > fixed by people upgrading. Fortunately, there are not so many tools
> > affected, and new version of those tools were released last
> > April/May. As I said, most distro have those in the pipe.
> > In-Kernel driver issues (the Orinoco driver problem). -> those
> > can be patched and fixed as we go along. I would not worry about
> > those.
> > Out-of-kernel issues (the ipw3945 driver problem). -> those
> > drivers need to be updated. That's the problem of living outside the
> > kernel. Very often those drivers are reactive with respect to kernel
> > API changes, rather than pro-active, so there is not much we can do.
> >
> > > It doesn't sound like it'll be too hard to arrange for the kernel to
> > > continue to work correctly with old userspace?
> >
> > Actually, it's impossible. New userspace can work across both
> > version, old userspace fails on new version.
>
> <rant>
> Well, please tell me now what number of people actually _will_ upgrade?
If you're using a distro, the distro maintainers should be making sure
versions are compatible. If you don't, well, then you need to be making
sure versions are compatible.
> And if they don't, will they use the -rc kernels? No, they won't, because
> of the apparent wireless breakage.
>
> This way we loose quite a few testers and the entire development
> process is affected, and that's _only_ because you have decided it
> will be _convenient_ to change the ABI. However, such changes affect
> _everyone_ and in a wrong way, except for a few people who actually want the
> change. They cause more damage than they are worth, so they should be avoided
> at all reasonable cost.
>
> It would be fair to introduce the change when distributions actually ship the
> userland tools capable of handling it, but not _now_.
Distributions _are_ shipping those tools already. The problem is more
with older distributions where, for example, the kernel gets upgraded
but other stuff does not. If a kernel upgrade happens, then the distro
needs to make sure userspace works with it. That's nothing new.
Dan
> </rant>
>
> Greetings,
> Rafael
>
>
next prev parent reply other threads:[~2006-10-02 21:01 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 8:59 wpa supplicant/ipw3945, ESSID last char missing Norbert Preining
2006-10-02 9:21 ` Alessandro Suardi
2006-10-02 11:32 ` Norbert Preining
2006-10-02 12:21 ` Alessandro Suardi
2006-10-02 12:46 ` Norbert Preining
2006-10-02 16:50 ` Norbert Preining
2006-10-02 16:58 ` Dan Williams
2006-10-02 18:15 ` Andrew Morton
2006-10-02 18:55 ` Jean Tourrilhes
2006-10-02 19:22 ` Dan Williams
2006-10-02 19:59 ` Jean Tourrilhes
2006-10-02 19:34 ` Dmitry Torokhov
2006-10-02 19:39 ` Jean Tourrilhes
2006-10-02 19:49 ` Dmitry Torokhov
2006-10-02 19:47 ` Rafael J. Wysocki
2006-10-02 21:00 ` Dan Williams [this message]
2006-10-02 21:26 ` Theodore Tso
2006-10-02 21:58 ` Jean Tourrilhes
2006-10-05 10:39 ` Keith Owens
2006-10-02 22:08 ` Alessandro Suardi
2006-10-03 12:12 ` Dan Williams
2006-10-03 12:49 ` John W. Linville
2006-10-03 13:38 ` Theodore Tso
2006-10-03 14:12 ` Dan Williams
2006-10-03 14:30 ` John W. Linville
2006-10-03 16:00 ` Theodore Tso
2006-10-03 17:03 ` Jean Tourrilhes
2006-10-03 16:52 ` Jean Tourrilhes
2006-10-03 17:23 ` Jean Tourrilhes
2006-10-03 17:38 ` Jean Tourrilhes
2006-10-03 17:40 ` Dan Williams
2006-10-03 22:30 ` Theodore Tso
2006-10-03 22:51 ` Jean Tourrilhes
2006-10-03 12:53 ` Alessandro Suardi
2006-10-03 16:41 ` Jean Tourrilhes
2006-10-10 6:29 ` Reinhard Tartler
2006-10-02 19:41 ` Jean Tourrilhes
2006-10-02 20:57 ` Dan Williams
2006-10-02 21:04 ` Jean Tourrilhes
2006-10-02 16:44 ` Lee Revell
2006-10-03 12:38 ` John W. Linville
2006-10-03 12:59 ` Theodore Tso
2006-10-03 15:54 ` Lee Revell
2006-10-03 16:27 ` Linus Torvalds
2006-10-03 18:05 ` John W. Linville
2006-10-03 18:19 ` Jeff Garzik
2006-10-03 18:38 ` Jean Tourrilhes
2006-10-03 18:59 ` Jeff Garzik
2006-10-03 19:48 ` Jean Tourrilhes
2006-10-03 19:52 ` Jean Tourrilhes
2006-10-03 21:40 ` John W. Linville
2006-10-03 21:48 ` Jeff Garzik
2006-10-03 22:27 ` Jean Tourrilhes
2006-10-03 22:41 ` Jeff Garzik
2006-10-04 2:10 ` Jouni Malinen
2006-10-03 21:59 ` Linus Torvalds
2006-10-03 22:16 ` Jean Tourrilhes
2006-10-03 22:30 ` Jeff Garzik
2006-10-04 18:10 ` Jean Tourrilhes
2006-10-04 18:32 ` Jeff Garzik
2006-10-04 18:42 ` Jean Tourrilhes
2006-10-04 18:38 ` Linus Torvalds
2006-10-04 18:59 ` Jean Tourrilhes
2006-10-04 19:12 ` Jeff Garzik
2006-10-04 19:21 ` Linus Torvalds
2006-10-04 19:52 ` Jean Tourrilhes
2006-10-04 20:12 ` Linus Torvalds
2006-10-04 20:19 ` Linus Torvalds
2006-10-04 20:47 ` Jean Tourrilhes
2006-10-04 22:26 ` Linus Torvalds
2006-10-05 0:26 ` Jean Tourrilhes
2006-10-05 2:19 ` Linus Torvalds
2006-10-05 15:20 ` Alessandro Suardi
2006-10-05 16:28 ` Jean Tourrilhes
2006-10-06 21:31 ` Pavel Machek
2006-10-04 21:08 ` John W. Linville
2006-10-04 23:29 ` Theodore Tso
2006-10-05 0:30 ` Jean Tourrilhes
2006-10-05 1:55 ` LEAP (was: wpa supplicant/ipw3945, ESSID last char missing) Jouni Malinen
2006-10-03 23:14 ` [ipw3945-devel] wpa supplicant/ipw3945, ESSID last char missing mabbas
2006-10-03 23:16 ` Theodore Tso
2006-10-03 23:31 ` Jean Tourrilhes
[not found] ` <20061003202754.ce69f03a.seanlkml@sympatico.ca>
2006-10-04 0:27 ` Sean
2006-10-04 0:30 ` Jean Tourrilhes
[not found] ` <20061003203646.60d9589a.seanlkml@sympatico.ca>
2006-10-04 0:36 ` Sean
2006-10-04 12:36 ` John W. Linville
2006-10-04 7:49 ` Johannes Berg
2006-10-05 16:35 ` Jean Tourrilhes
2006-10-05 16:43 ` Jeff Garzik
2006-10-05 17:42 ` Erik Andersen
2006-10-05 17:45 ` Jeff Garzik
2006-10-05 18:36 ` John W. Linville
2006-10-04 7:50 ` Johannes Berg
2006-10-03 19:08 ` Dmitry Torokhov
2006-10-03 19:49 ` Jean Tourrilhes
2006-10-04 2:21 ` Jouni Malinen
2006-10-04 7:33 ` Arjan van de Ven
2006-10-04 12:39 ` John W. Linville
2006-10-03 18:31 ` Hugh Dickins
2006-10-03 18:40 ` Jean Tourrilhes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1159822831.11771.5.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=akpm@osdl.org \
--cc=alessandro.suardi@gmail.com \
--cc=hostap@shmoo.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=preining@logic.at \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox