linux-kernel - Re: Fwd: w_scan hangs on 6.3.7 and does not react on kill -9

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: <98909a2f-cb55-b732-409c-ad14c802bf13@leemhuis.info>
Date:   Tue, 13 Jun 2023 13:59:54 +0200
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Lukasz Kalamlacki <kalamlacki@...il.com>,
        Hyunwoo Kim <imv4bel@...il.com>,
        Sasha Levin <sashal@...nel.org>,
        Stefan Lippers-Hollmann <s.l-h@....de>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Media Mailing List <linux-media@...r.kernel.org>
Subject: Re: Fwd: w_scan hangs on 6.3.7 and does not react on kill -9



On 13.06.23 13:23, Bagas Sanjaya wrote:
> On 6/12/23 20:52, Bagas Sanjaya wrote:
>> Hi,
>>
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>
>>> w_scan tool on kernel 6.3.7 hangs so badly that it cannot be killed by kill -9 
>>> I tried also w_scan_cpp 20230604 but it also fails I have 2040:8268 Hauppauge soloHD device as reported by lsusb. During reboot of the OS it prints a lot of kernel errors but it is after syslog is killed I guess and in syslog messages I do not see anything. On default Debian kernel 5.10.0-23 this problem does not exists.
>>
>>
>> See Bugzilla for the full thread and attached dmesg and kernel config.
>>
>> Lukasz: On what hardware you have this regression? Also, it is really
>> helpful if you can perform bisection (as outlined
>> in Documentation/admin-guide/bug-bisect.html) to find the culprit,
>> when developers can't figure it out by inspecting the code alone.
>> Last but not least, please also try latest mainline (currently v6.4-rc6).
>>
>> Anyway, I'm adding it to regzbot:
>>
>> #regzbot introduced: v5.10..v6.3 https://bugzilla.kernel.org/show_bug.cgi?id=217540
>> #regzbot title: w_scan zombie (unkillable) on kernel v6.3
> 
> Another reporter on Bugzilla with similar regression as this one had
> bisected the culprit, so:
> 
> Hyunwoo Kim: It looks like this regression is caused by a backported
> commit of yours. Would you like to take a look on it?
> 
> #regzbot introduced: 8994830135b38b

TWIMC, revert for mainline already in preparation, for details see:

https://lore.kernel.org/all/23d5f9d6-f0db-a9af-1291-e9d6ac3cd126@leemhuis.info/

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.

#regzbot monitor: https://lore.kernel.org/all/20230613053314.70839926@mir/
#regzbot monitor:
https://lore.kernel.org/all/20230609082238.3671398-1-mchehab@kernel.org/