mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Lukasz Kalamlacki <kalamlacki@gmail.com>,
	Hyunwoo Kim <imv4bel@gmail.com>, Sasha Levin <sashal@kernel.org>,
	Stefan Lippers-Hollmann <s.l-h@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Fwd: w_scan hangs on 6.3.7 and does not react on kill -9
Date: Tue, 13 Jun 2023 19:33:40 +0700	[thread overview]
Message-ID: <f5bcc9d5-2022-8c28-b84c-806e9c9d1d20@gmail.com> (raw)
In-Reply-To: <98909a2f-cb55-b732-409c-ad14c802bf13@leemhuis.info>

On 6/13/23 18:59, Linux regression tracking (Thorsten Leemhuis) wrote:
> 
> 
> 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/
> 

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/23d5f9d6-f0db-a9af-1291-e9d6ac3cd126@leemhuis.info/

-- 
An old man doll... just what I always wanted! - Clara


      reply	other threads:[~2023-06-13 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 13:52 Bagas Sanjaya
2023-06-13 11:23 ` Bagas Sanjaya
2023-06-13 11:59   ` Linux regression tracking (Thorsten Leemhuis)
2023-06-13 12:33     ` Bagas Sanjaya [this message]

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=f5bcc9d5-2022-8c28-b84c-806e9c9d1d20@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=imv4bel@gmail.com \
    --cc=kalamlacki@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=s.l-h@gmx.de \
    --cc=sashal@kernel.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

all inboxes | Powered by JetHome®