Skip to contentSkip to conversation

w_scan hangs on 6.3.7 and does not react on kill -9

DISCUSSION Bagas Sanjaya 2 participants 4 messages Jun 12, 2023 – Jun 13, 2023

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

Quoted 2 lines

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

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217540

Signature · 1 line
An old man doll... just what I always wanted! - Clara
#1 lore raw
Quoted 16 lines · Bagas Sanjaya

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

Quoted 2 lines

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).

Quoted 5 lines

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

Thanks.

Signature · 1 line
An old man doll... just what I always wanted! - Clara
#2 lore raw
Quoted 22 lines · Bagas Sanjaya
Quoted 16 lines · Bagas Sanjaya

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

Quoted 2 lines

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).

Quoted 4 lines

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

Quoted 7 lines

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/[email protected]/

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/[email protected]/

#3 lore raw
Quoted 28 lines · Linux regression tracking (Thorsten Leemhuis)
Quoted 25 lines · Bagas Sanjaya
Quoted 16 lines · Bagas Sanjaya

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

Quoted 2 lines

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).

Quoted 4 lines

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:

Quoted 9 lines
Quoted 4 lines

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/[email protected]/

Hi Thorsten, thanks for additional discussion link. Telling regzbot:

#regzbot fix: Revert "media: dvb-core: Fix use-after-free on race condition at dvb_frontend" #regzbot monitor: https://lore.kernel.org/all/[email protected]/

Signature · 1 line
An old man doll... just what I always wanted! - Clara