netdev - Re: After kernel 6.3.7 or 6.3.8 b43 driver fails

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <18f4cb13-9b7d-e202-333e-43c76d8c7290@lwfinger.net>
Date: Sat, 24 Jun 2023 11:22:40 -0500
From: Larry Finger <Larry.Finger@...inger.net>
To: Linux regressions mailing list <regressions@...ts.linux.dev>,
 Arnd Bergmann <arnd@...db.de>, Michael Büsch <m@...s.ch>,
 Bagas Sanjaya <bagasdotme@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Wireless <linux-wireless@...r.kernel.org>,
 Netdev <netdev@...r.kernel.org>, kernel test robot <lkp@...el.com>,
 Simon Horman <simon.horman@...igine.com>, Kalle Valo <kvalo@...nel.org>,
 sardonimous@...mail.com
Subject: Re: After kernel 6.3.7 or 6.3.8 b43 driver fails

On 6/24/23 09:00, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 24.06.23 11:29, Arnd Bergmann wrote:
>> On Sat, Jun 24, 2023, at 10:50, Michael Büsch wrote:
>>> On Sat, 24 Jun 2023 08:44:15 +0700
>>> Bagas Sanjaya <bagasdotme@...il.com> wrote:
>>>>> I suspect change introduced when addressing a compiler warning
>>>>> cased the error.
>>>>>
>>>>> https://patchwork.kernel.org/project/linux-wireless/patch/20230516183442.536589-1-arnd%40kernel.org/
>>>
>>> I doubt it.
>>> This patch affects the device initialization code. But the crash is in
>>> the transmit path.
>>> Can you please double check by manually reverting the patch?
>>
>> I'm travelling at the moment and can't easily check it, but I would
>> expect that my patch has no effect on the generated object code [...]
> 
> Michael, Arnd, thx for the replies. To you and everyone else that looked
> into this: sorry for the trouble this caused.
> 
> The reporter's guess was wrong, as the reporter meanwhile confirmed in
> the bugzilla ticket that the problem started to happen earlier.
> 
> Bagas, please be a bit more careful and don't blame a specific commit
> unless it's was found by bisection, a revert through a lucky guess, a
> statement from a developer, or something like that. In cases like this
> it would have been better to sent the developers of said commit a quick
> mail along the lines of "could you imagine that this change could lead
> to the problem the reporter described". But even that might be too much
> in a case like this, as too many of such false alarms and inquiries will
> make developers start hating or ignoring regression tracking in general
> or mails from you or me – and that is something that must be avoided, as
> without help from developers regression tracking becomes a lot harder or
> impossible.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
> 
> P.S.: Updating regzbot status, while at it:

The OP definitely needs to bisect this problem. The only system that I have that 
runs b43 is a PowerBook G4 with a ppc32 CPU. That box has successfully run b43 
for every release up to 6.4.0-rc7. I have seen no problems in recent kernels.

Larry