Re: [PATCH v5] misc: fastrpc: check qcom_scm_assign_mem() return in rpmsg_probe
From: Xingjing Deng
Date: Tue Jan 27 2026 - 21:35:06 EST
I got it, I'll note that this is a private static analysis tool, and
I'll release the next version of the patch
Xingjing Deng <micro6947@xxxxxxxxx> 于2026年1月28日周三 10:29写道:
>
> I understand the current situation. I need to record which static
> analysis tool I used to identify this issue and clarify that no actual
> testing was performed. However, I have a question: my static analysis
> tool is not open-source, so how should I document this?
>
> Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> 于2026年1月27日周二 15:10写道:
> >
> > 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