From: "Maximilian Böhm" <maximilian.boehm@elbmurf.de>
To: Pavel Skripkin <paskripkin@gmail.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: hverkuil-cisco@xs4all.nl, sashal@kernel.org,
linux-media@vger.kernel.org, Brad Love <brad@nextdimension.cc>
Subject: Re: Kernel hangs after DVB patch from July 2021 with Hauppauge WinTV dualHD
Date: Thu, 20 Jan 2022 20:29:45 +0100 [thread overview]
Message-ID: <a0ba3685-8c59-cb89-7f81-280c38a92c40@elbmurf.de> (raw)
In-Reply-To: <a0e25415-2db7-bea0-b00c-f1b4bf84d0d6@gmail.com>
Hey Pavel,
I would prefer reverting your use-after-free change. I’m still on Linux 5.15.2 to avoid this issue. I’m not sure if I understand your last mails correctly, did you already revert the change or did you just offer to do it? Anyway, reverting locally wouldn’t be feasible long-term.
If I could help eliminating this bug, I would gladly offer my system for a remote hacking session via ssh or Teamviewer or try other patch ideas.
Btw, found this forum thread describing the same original problem (which is forcing me to use usbreset after standby) on Windows, so this probably is a bug in the tuner hardware, not in the Linux driver: https://www.dvbviewer.tv/forum/topic/63002-hauppauge-wintv-dualhd-stick-geht-oft-nicht-nach-standby/
If I were to submit an official "device quirk" for the Linux kernel, would it be affected of your use-after-free change too? Nobody knows, I guess?
Regards
Maximilian Böhm
Am 06.01.22 um 12:57 schrieb Pavel Skripkin:
>> Anyway, you can revert my patch locally and use your device. I
>> understand, that this approach is the best one, but anyway revert will
>
> ^^^^
>
> I've missed "not". Please, don't get me wrong :) Reverting something
> locally to work with upstream device is never a good thing.
>
>
>
> With regards,
> Pavel Skripkin
next prev parent reply other threads:[~2022-01-20 19:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 1:09 Kernel hangs after DVB patch from July 2021 with Hauppauge WinTV dualHD Maximilian Böhm
2021-12-18 9:15 ` Mauro Carvalho Chehab
2021-12-18 14:23 ` Pavel Skripkin
2021-12-18 22:50 ` Maximilian Böhm
2021-12-20 14:39 ` Pavel Skripkin
2022-01-04 17:22 ` Maximilian Böhm
2022-01-04 17:31 ` Pavel Skripkin
2022-01-04 17:58 ` Maximilian Böhm
2022-01-06 11:54 ` Pavel Skripkin
2022-01-06 11:57 ` Pavel Skripkin
2022-01-20 19:29 ` Maximilian Böhm [this message]
2022-01-20 19:37 ` [PATCH] Revert "media: em28xx: add missing em28xx_close_extension" Pavel Skripkin
2022-01-21 18:30 ` Maximilian Böhm
2022-01-20 19:42 ` Kernel hangs after DVB patch from July 2021 with Hauppauge WinTV dualHD Pavel Skripkin
2022-02-17 11:14 ` Hans Verkuil
2022-02-18 0:16 ` Maximilian Böhm
2022-02-18 7:58 ` Hans Verkuil
2021-12-18 20:33 ` Robert Schlabbach
2021-12-18 20:51 ` Pavel Skripkin
2021-12-18 23:19 ` Maximilian Böhm
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=a0ba3685-8c59-cb89-7f81-280c38a92c40@elbmurf.de \
--to=maximilian.boehm@elbmurf.de \
--cc=brad@nextdimension.cc \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=paskripkin@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.