From: "Michael Büsch" <m@bues.ch>
To: Wirz <spam-rxbgZ4vWfLhdz0/ABlLGQA@public.gmane.org>
Cc: linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
b43-dev-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Matt Mackall <mpm-VDJrAJ4Gl5ZBDgjK7y7TUQ@public.gmane.org>,
Herbert Xu
<herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org>,
linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: b43 crashes on rmmod (bcm4331)
Date: Wed, 13 Jun 2018 15:28:12 +0200 [thread overview]
Message-ID: <20180613152812.5596b460@wiggum> (raw)
In-Reply-To: <6b84a788-e11f-91db-309c-4ff79fdcad66-rxbgZ4vWfLhdz0/ABlLGQA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
On Wed, 13 Jun 2018 16:07:02 +0300
Wirz <spam-rxbgZ4vWfLhdz0/ABlLGQA@public.gmane.org> wrote:
> >>>> CONFIG_B43_HWRNG completely switches off hwrng support in b43.
> >>>> I don't see how a change in hwrng core could still lead to a crash in
> >>>> b43 with this option switched off.
> >>>>
> >>>> What do you mean by "manually in the .config"?
> >>>
> >>> What I meant is, that I have outcommented the line 'CONFIG_B43_HWRNG=y'
> >>> in .config.
> >>>
> >>>> Can you try to properly switch off the setting with make menuconfig and
> >>>> then recompile everything from scratch (make clean)?
> >>>
> >>> I was intending to do that before, but I cannot find the option for
> >>> that. Searching for b43_hwrng in menuconfig only shows the dependencies
> >>> of that option, and the Kconfig file where it is defined, but not the
> >>> path in menuconfig. Do I indirectly set CONFIG_B43_HWRNG through the
> >>> parameters it depends on? I'm sorry, but this is obviously above my
> >>> level of expertise ...
> >>
> >> Whoops, sorry. You are right. This is an automatic config option.
> >> That also means your manual editing of .config would be overridden.
> >>
> >> 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.
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-13 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <75e4b424-4c75-5abd-1ef0-c2537d329b10@lukas-wirz.de>
[not found] ` <d9896c10-87bb-8362-f302-8b1888c3421c@lukas-wirz.de>
[not found] ` <20180609171159.59b5209c@wiggum>
[not found] ` <6a78c68e-1062-5ad8-876c-f7d4c49ea492@lukas-wirz.de>
[not found] ` <20180609220130.3ceb834f@wiggum>
[not found] ` <e72be8db-77ba-408c-c5e5-351d722e09e8@lukas-wirz.de>
[not found] ` <20180611224634.28ccd288@wiggum>
[not found] ` <7d564b8b-2b71-73f6-3ae7-ede0187a4151@lukas-wirz.de>
[not found] ` <20180613122751.2fe89737@wiggum>
[not found] ` <538cd7b7-8d63-1795-7bfc-69231d2bf3c0@lukas-wirz.de>
[not found] ` <20180613130905.420695e7@wiggum>
2018-06-13 12:01 ` b43 crashes on rmmod (bcm4331) Michael Büsch
2018-06-13 13:07 ` Wirz
[not found] ` <6b84a788-e11f-91db-309c-4ff79fdcad66-rxbgZ4vWfLhdz0/ABlLGQA@public.gmane.org>
2018-06-13 13:28 ` Michael Büsch [this message]
2018-06-14 9:47 ` Wirz
[not found] ` <6bef30e0-9405-2ddd-d1eb-612b4d4e3382-rxbgZ4vWfLhdz0/ABlLGQA@public.gmane.org>
2018-06-14 16:26 ` Michael Büsch
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=20180613152812.5596b460@wiggum \
--to=m@bues.ch \
--cc=b43-dev-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org \
--cc=linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mpm-VDJrAJ4Gl5ZBDgjK7y7TUQ@public.gmane.org \
--cc=spam-rxbgZ4vWfLhdz0/ABlLGQA@public.gmane.org \
/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