From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C0E9C136E3F; Wed, 28 Jan 2026 05:48:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769579317; cv=none; b=SMLwbB3ZTfp1mGVO6+2kzYOZe6rKywFdpYhPkq+B4Nn2hvoHCALCTwlt2fNzqqbz5fjE1zcaaYPZPeFfHaonnH/fnaY4ZkikRZddQ8Xkmpx1bHhA82IrdSBpP8C3oJ9P+6xv+RA+LVhMYfopehUQPVqDKYNOkFs2amSNwTrw1XQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769579317; c=relaxed/simple; bh=uUU1GFk6W9A2OhC/0i9QZZ4frb720ycWNzcpj8viw1c=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=EHpjcnivo3LH5BGZup0T0n/LRaHvBCPle+ceZObQtUbuZkGMarxkhYVvZQBp+G6z8A6yLazlf6hdYEbKgbsH3UX9rJK79LfbcTotlJ+U0+6GnsGxgmI7CSB6XuGNi0w7Tnz0Ug6mbc/SI5AtThQBBCCChac4PzY48T8yucD2lEk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=XF/doAP2; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="XF/doAP2" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D34D8C116C6; Wed, 28 Jan 2026 05:48:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1769579317; bh=uUU1GFk6W9A2OhC/0i9QZZ4frb720ycWNzcpj8viw1c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XF/doAP2FUIHDmBvQznqagpDoIj6aOJq6sC881I/0ERPwAmVrz3nOglVNpUzyfPz3 HIf0gjszE7GZ8D/aZbv8GHN9c3p0XIugnwLf+mSLmTzIwm9qZcOt22fkDNNJaTKlPS DFP4FiTTAFvzAwGYWh0pU0/+DWd8gm4iDv2RmSkI= Date: Wed, 28 Jan 2026 06:48:33 +0100 From: Greg KH To: Xingjing Deng 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 , stable@vger.kernel.org Subject: Re: [PATCH v6] misc: fastrpc: check qcom_scm_assign_mem() return in rpmsg_probe Message-ID: <2026012851-precut-apostle-1d38@gregkh> References: <20260128033454.2614886-1-xjdeng@buaa.edu.cn> Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260128033454.2614886-1-xjdeng@buaa.edu.cn> On Wed, Jan 28, 2026 at 11:34:54AM +0800, Xingjing Deng wrote: > In the SDSP probe path, qcom_scm_assign_mem() is used to assign the > reserved memory to the configured VMIDs, but its return value was not checked. > > Fail the probe if the SCM call fails to avoid continuing with an > unexpected/incorrect memory permission configuration. > > This issue was detected by a private static analysis tool. As per our documentation, you need to say a bit more than this about your tool. Please read Documentation/process/researcher-guidelines.rst for the details. thanks, greg k-h