[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230329213216.7b0447e9@kernel.org>
Date: Wed, 29 Mar 2023 21:32:16 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Sricharan R <quic_srichara@...cinc.com>
Cc: <mani@...nel.org>, <manivannan.sadhasivam@...aro.org>,
<davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
<linux-arm-msm@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net: qrtr: Do not do DEL_SERVER broadcast after
DEL_CLIENT
On Wed, 29 Mar 2023 18:37:30 +0530 Sricharan R wrote:
> When the qrtr socket is released, qrtr_port_remove gets called, which
> broadcasts a DEL_CLIENT. After this DEL_SERVER is also additionally
> broadcasted, which becomes NOP, but triggers the below error msg.
>
> "failed while handling packet from 2:-2", since remote node already
> acted upon on receiving the DEL_CLIENT, once again when it receives
> the DEL_SERVER, it returns -ENOENT.
>
> Fixing it by not sending a 'DEL_SERVER' to remote when a 'DEL_CLIENT'
> was sent for that port.
You use the word "fix" so please add a Fixes tag.
> Signed-off-by: Ram Kumar D <quic_ramd@...cinc.com>
> Signed-off-by: Sricharan R <quic_srichara@...cinc.com>
Spell out full names, please.
Powered by blists - more mailing lists