From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Alper Ak <alperyasinak1@gmail.com>,
Markus Elfring <Markus.Elfring@web.de>
Cc: linux-media@vger.kernel.org,
Jackson Lee <jackson.lee@chipsnmedia.com>,
Nas Chung <nas.chung@chipsnmedia.com>,
LKML <linux-kernel@vger.kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] media: chips-media: wave5: Fix possible ERR_PTR deference
Date: Tue, 20 Oct 2026 15:16:39 -0400 [thread overview]
Message-ID: <ecdc24931abc4f84bc0bd8e2025f77406ab476b2.camel@collabora.com> (raw)
In-Reply-To: <92af2072500ec68990cc643256929044bc54e184.camel@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
Hi,
Le vendredi 06 mars 2026 à 08:50 -0500, Nicolas Dufresne a écrit :
> Hi,
>
> Le vendredi 06 mars 2026 à 09:32 +0300, Alper Ak a écrit :
> > Hello everyone, look like this patch hasn't been applied. Did I miss
> > something I needed to do to get it applied? If there is anything I
> > need to do, please let me know.
>
> You received an Ack from the maintainer, and got a tested buy. But the patch has
> been submitted while the merge window was closed, which is fine, but means there
> is a small delay. It should be processed within the next two weeks. Your subject
> suggest a theoretical bug, so it has not be been prioritized over other patches
> in the queue.
I discovered now that I missed this one in latest fixes batchs, be reassured
that its not assigned to me in patchwork and will be applied soon.
Nicolas
>
> regards,
> Nicolas
>
> >
> > Markus Elfring <Markus.Elfring@web.de>, 13 Şub 2026 Cum, 14:38
> > tarihinde şunu yazdı:
> > >
> > > …
> > > > or ERR_PTR() on failure. The return value was not checked and in the
> > >
> > > error pointer
> > >
> > > …
> > > > Add proper IS_ERR() check after kthread_run(), log the error, set
> > > > dev->irq_thread to NULL and fail the probe to prevent the driver
> > > > from operating in a broken state.
> > > …
> > >
> > > See also once more:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v6.19#n34
> > >
> > >
> > > Would a summary phrase like “Prevent error pointer dereference in
> > > wave5_vpu_probe()”
> > > be more appropriate?
> > >
> > > Regards,
> > > Markus
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-20 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 10:32 Alper Ak
2026-02-11 9:12 ` Nas Chung
[not found] ` <CAGpma=5ONpUwnOStE+cLpJcqrb-=ZYT4krx=whgeAup1ACERQg@mail.gmail.com>
2026-02-13 5:38 ` Nas Chung
2026-02-13 11:38 ` Markus Elfring
2026-03-06 6:32 ` Alper Ak
2026-03-06 6:54 ` Markus Elfring
2026-03-06 13:50 ` [PATCH] " Nicolas Dufresne
2026-10-20 19:16 ` Nicolas Dufresne [this message]
2026-10-21 9:04 ` Markus Elfring
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=ecdc24931abc4f84bc0bd8e2025f77406ab476b2.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=Markus.Elfring@web.de \
--cc=alperyasinak1@gmail.com \
--cc=hverkuil+cisco@kernel.org \
--cc=jackson.lee@chipsnmedia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.com \
/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®