From: Markus Elfring <Markus.Elfring@web.de>
To: Dawei Feng <dawei.feng@seu.edu.cn>, Zilin Guan <zilin@seu.edu.cn>,
linux-media@vger.kernel.org, kernel-list@raspberrypi.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Jianhao Xu <jianhao.xu@seu.edu.cn>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Subject: Re: [PATCH] media: bcm2835-unicam: fix dummy buffer double free when register fails
Date: Mon, 18 May 2026 10:37:10 +0200 [thread overview]
Message-ID: <a77b88d4-249e-4c9e-b529-72127bbb1103@web.de> (raw)
In-Reply-To: <20260515152529.1007540-1-dawei.feng@seu.edu.cn>
…
> Set dummy_buf_cpu_addr to NULL after dma_free_coherent() in both the
> local error path and unicam_unregister_nodes() so later cleanup skips
…
so that?
> The bug was first flagged by an experimental analysis tool we are
> developing for kernel memory-management bugs while analyzing
> v6.13-rc1. The tool is still under development and is not yet publicly
> available. Manual inspection confirms that the bug is still
> present in v7.1-rc3.
Under which circumstances will the mentioned software revision gap
be adjusted accordingly?
Regards,
Markus
prev parent reply other threads:[~2026-05-18 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 15:25 [PATCH] media: bcm2835-unicam: fix dummy buffer double free when register fails Dawei Feng
2026-05-18 8:37 ` Markus Elfring [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=a77b88d4-249e-4c9e-b529-72127bbb1103@web.de \
--to=markus.elfring@web.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dawei.feng@seu.edu.cn \
--cc=florian.fainelli@broadcom.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=kernel-list@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=zilin@seu.edu.cn \
/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