From: Greg KH <gregkh@suse.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
greg@kroah.com, torvalds@linux-foundation.org,
akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk,
linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
roman-vl@meta.ua, "Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: [17/26] b43: refuse to load unsupported firmware
Date: Sat, 19 Nov 2011 11:05:59 -0800 [thread overview]
Message-ID: <20111119190559.GC30197@suse.de> (raw)
In-Reply-To: <1321723330.2885.145.camel@deadeye>
On Sat, Nov 19, 2011 at 05:22:10PM +0000, Ben Hutchings wrote:
> On Fri, 2011-11-18 at 16:02 -0800, Greg KH wrote:
> > 3.1-stable review patch. If anyone has any objections, please let me know.
> >
> > ------------------
> >
> > [This patch is supposed to be applied in 3.1 (and maybe older) branches only.]
> >
> > New kernels support newer firmware that users may try to incorrectly use
> > with older kernels. Display error and explain the problem in such a case
> >
> > Signed-off-by: RafaÅ MiÅecki <zajec5@gmail.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> >
> > ---
> > drivers/net/wireless/b43/main.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > --- a/drivers/net/wireless/b43/main.c
> > +++ b/drivers/net/wireless/b43/main.c
> > @@ -2508,6 +2508,13 @@ static int b43_upload_microcode(struct b
> > b43_print_fw_helptext(dev->wl, 1);
> > err = -EOPNOTSUPP;
> > goto error;
> > + } else if (fwrev >= 598) {
> > + b43err(dev->wl, "YOUR FIRMWARE IS TOO NEW. Support for "
> > + "firmware 598 and up requires kernel 3.2 or newer. You "
> > + "have to install older firmware or upgrade kernel.\n");
> > + b43_print_fw_helptext(dev->wl, 1);
> > + err = -EOPNOTSUPP;
> > + goto error;
> [...]
>
> Again, I strongly object to this way of handling the incompatibility.
> The revision check is fine, but the solution must be to assign a
> different filename for the newer revisions. The changes to 3.0/3.1
> should be deferred until this is resolved.
You can object, however the driver author and maintainer wants it done
this way for now, so that's a valid solution that I have to accept. It
solves real bugs that people have already hit when running the 3.0 and
3.1 kernels. Propagating a userspace tool change for those systems
would be much harder, if not impossible, don't you think? It would also
require a much more intrusive change to the driver infrastructure to
handle such a proposed change.
thanks,
greg k-h
next prev parent reply other threads:[~2011-11-19 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111119000336.GA8452@kroah.com>
2011-11-19 0:02 ` [17/26] b43: refuse to load unsupported firmware Greg KH
2011-11-19 17:22 ` Ben Hutchings
2011-11-19 19:05 ` Greg KH [this message]
2011-11-19 19:49 ` Ben Hutchings
[not found] <20111119000026.GA6679@kroah.com>
2011-11-18 23:58 ` Greg KH
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=20111119190559.GC30197@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=b43-dev@lists.infradead.org \
--cc=ben@decadent.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=roman-vl@meta.ua \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zajec5@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).