[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2026012758-sacred-slouchy-45ca@gregkh>
Date: Tue, 27 Jan 2026 08:10:41 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Xingjing Deng <micro6947@...il.com>
Cc: Bjorn Andersson <andersson@...nel.org>, srini@...nel.org,
amahesh@....qualcomm.com, arnd@...db.de,
dri-devel@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, Xingjing Deng <xjdeng@...a.edu.cn>,
stable@...r.kernel.org
Subject: Re: [PATCH v5] misc: fastrpc: check qcom_scm_assign_mem() return in
rpmsg_probe
On Tue, Jan 27, 2026 at 10:18:38AM +0800, Xingjing Deng wrote:
> I identified this issue through static program analysis. All other
> callers of this function validate its return value, so I believe a
> validation check should also be added here.
Please don't top-post :(
Anyway, you MUST properly document the tools used to find issues like
this in your changelog text, as our rules require. Please do so.
thanks,
greg k-h
Powered by blists - more mailing lists