[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7b9694ea-a4fc-43bf-b58b-8c479af18140@quicinc.com>
Date: Mon, 23 Dec 2024 16:11:51 +0530
From: Anandu Krishnan E <quic_anane@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
CC: <srinivas.kandagatla@...aro.org>, <linux-arm-msm@...r.kernel.org>,
<gregkh@...uxfoundation.org>, <quic_bkumar@...cinc.com>,
<linux-kernel@...r.kernel.org>, <quic_chennak@...cinc.com>,
<dri-devel@...ts.freedesktop.org>, <arnd@...db.de>,
stable
<stable@...nel.org>
Subject: Re: [PATCH v2 1/2] misc: fastrpc: Deregister device nodes properly in
error scenarios
On 12/23/2024 3:49 PM, Dmitry Baryshkov wrote:
> On Mon, Dec 23, 2024 at 03:31:00PM +0530, Anandu Krishnan E wrote:
>> During fastrpc_rpmsg_probe, if secure device node registration
>> succeeds but non-secure device node registration fails, the secure
>> device node deregister is not called during error cleanup. Add proper
>> exit paths to ensure proper cleanup in case of error.
>>
>> Fixes: 3abe3ab3cdab ("misc: fastrpc: add secure domain support")
>> Cc: stable <stable@...nel.org>
>> Signed-off-by: Anandu Krishnan E <quic_anane@...cinc.com>
>> ---
>> drivers/misc/fastrpc.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> This triggers checkpatch warning. If it is due to c&p from some internal
> documentation, please fix it too.
Understood. I will fix the checkpatch warning in the next spin.
-Anandu
>
>>
>> diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c
>> index 48d08eeb2d20..ff144f0aa337 100644
>> --- a/drivers/misc/fastrpc.c
>> +++ b/drivers/misc/fastrpc.c
>> @@ -2344,7 +2344,7 @@ static int fastrpc_rpmsg_probe(struct rpmsg_device *rpdev)
>>
>> err = fastrpc_device_register(rdev, data, false, domains[domain_id]);
>> if (err)
>> - goto fdev_error;
>> + goto populate_error;
>> break;
>> default:
>> err = -EINVAL;
>> --
>> 2.17.1
>>
>
Powered by blists - more mailing lists