linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: Wirz <spam@lukas-wirz.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	b43-dev@lists.infradead.org, Matt Mackall <mpm@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org
Subject: Re: b43 crashes on rmmod (bcm4331)
Date: Thu, 14 Jun 2018 18:26:36 +0200	[thread overview]
Message-ID: <20180614182636.1b92d7df@wiggum> (raw)
In-Reply-To: <6bef30e0-9405-2ddd-d1eb-612b4d4e3382@lukas-wirz.de>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

On Thu, 14 Jun 2018 12:47:19 +0300
Wirz <spam@lukas-wirz.de> wrote:

> >>>> You can edit drivers/net/wireless/broadcom/b43/Kconfig
> >>>> go to the section config B43_HWRNG
> >>>> and change 'default y' to 'default n'
> >>>>
> >>>> That should disable it.    
> >>>
> >>>
> >>>
> >>> Could you please also try the attached patch?
> >>> There seems to be a problem in hwrng core in that it does not disable
> >>> the current RNG, if the new RNG fails to initialize.
> >>> I don't know if that's the problem here, though.    
> >>
> >> Ok. Do I apply your patch to the first version that fails for me, and
> >> revert my change to Kconfig?  
> > 
> > 
> > Yes, please test the patch with a version that would otherwise fail.
> > You can use 4.16 or the latest kernel for that. I created it with latest
> > linus' version.  
> 
> I tested both suggested cases.  When I disable B43_HWRNG by editing
> Kconfig, 'rmmod b43' succeeds in the first version where it previously
> failed.  When I apply your patch on top of an unmodified 4.16 it also
> succeeds.


Thank you _very_ much for testing.

I will submit this patch to the hw_random maintainers.

-- 
Michael

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-06-14 16:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 19:55 b43 crashes on rmmod (bcm4331) Wirz
2018-06-09 12:08 ` Wirz
2018-06-09 15:11   ` Michael Büsch
2018-06-09 19:46     ` Wirz
2018-06-09 20:01       ` Michael Büsch
2018-06-11 20:09         ` Wirz
2018-06-11 20:46           ` Michael Büsch
2018-06-13  9:25             ` Wirz
2018-06-13 10:27               ` Michael Büsch
2018-06-13 11:01                 ` Wirz
2018-06-13 11:09                   ` Michael Büsch
2018-06-13 12:01                     ` Michael Büsch
2018-06-13 13:07                       ` Wirz
2018-06-13 13:28                         ` Michael Büsch
2018-06-14  9:47                           ` Wirz
2018-06-14 16:26                             ` Michael Büsch [this message]
2018-06-14 19:18                               ` Wirz

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=20180614182636.1b92d7df@wiggum \
    --to=m@bues.ch \
    --cc=b43-dev@lists.infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=spam@lukas-wirz.de \
    /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).