From: Greg KH <gregkh@linuxfoundation.org>
To: Xingjing Deng <micro6947@gmail.com>
Cc: srini@kernel.org, amahesh@qti.qualcomm.com, arnd@arndb.de,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, Xingjing Deng <xjdeng@buaa.edu.cn>,
stable@vger.kernel.org
Subject: Re: [PATCH v4] misc: fastrpc: possible double-free of cctx->remote_heap
Date: Wed, 28 Jan 2026 07:05:43 +0100 [thread overview]
Message-ID: <2026012807-engross-pettiness-4cab@gregkh> (raw)
In-Reply-To: <20260128042600.2641857-1-xjdeng@buaa.edu.cn>
On Wed, Jan 28, 2026 at 12:26:00PM +0800, Xingjing Deng wrote:
> This issue was detected by a private static analysis tool.
As stated before, you need more info here, otherwise everyone would just
use a generic line like this and that's not going to help anyone,
including you, out.
thanks,
greg k-h
prev parent reply other threads:[~2026-01-28 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 4:26 [PATCH v4] misc: fastrpc: possible double-free of cctx->remote_heap Xingjing Deng
2026-01-28 6:05 ` Greg KH [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=2026012807-engross-pettiness-4cab@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=micro6947@gmail.com \
--cc=srini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xjdeng@buaa.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