The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qianchang Zhao <pioooooooooip@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Zhitong Liu <liuzhitong1993@gmail.com>
Subject: Re: [PATCH] nfc: llcp: stop processing on LLCP_CLOSED in nfc_llcp_recv_hdlc()
Date: Wed, 17 Dec 2025 08:35:48 +0100	[thread overview]
Message-ID: <07e506c9-21f7-4d4a-ada3-ad0004acf6fc@kernel.org> (raw)
In-Reply-To: <20251217011538.16029-1-pioooooooooip@gmail.com>

On 17/12/2025 02:15, Qianchang Zhao wrote:
> nfc_llcp_sock_get() takes a reference on the LLCP socket via sock_hold().
> 
> In nfc_llcp_recv_hdlc(), the LLCP_CLOSED branch releases the socket lock and
> drops the reference, but the function continues to operate on llcp_sock/sk and
> later runs release_sock() and nfc_llcp_sock_put() again on the common exit path.
> 
> Return immediately after the CLOSED cleanup to avoid refcount/lock imbalance and
> to avoid using the socket after dropping the reference.
> 
> Reported-by: Qianchang Zhao <pioooooooooip@gmail.com>
> Reported-by: Zhitong Liu <liuzhitong1993@gmail.com>

No, drop. Same comments as for other patch.

Organize your patches in a patchset. Don't send independent works, it's
just more work for maintainers to apply.


> Cc: stable@vger.kernel.org
> Signed-off-by: Qianchang Zhao <pioooooooooip@gmail.com>
> ---
>  net/nfc/llcp_core.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/net/nfc/llcp_core.c b/net/nfc/llcp_core.c
> index beeb3b4d2..be01ec9f4 100644
> --- a/net/nfc/llcp_core.c
> +++ b/net/nfc/llcp_core.c
> @@ -1089,6 +1089,7 @@ static void nfc_llcp_recv_hdlc(struct nfc_llcp_local *local,
>  	if (sk->sk_state == LLCP_CLOSED) {
>  		release_sock(sk);
>  		nfc_llcp_sock_put(llcp_sock);
> +		return;

Answer my previous questions from the private thread.

>  	}
>  
>  	/* Pass the payload upstream */


Best regards,
Krzysztof

      reply	other threads:[~2025-12-17  7:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <307c2afe-8e8e-4edf-b6d1-1056fe8949f6@kernel.org>
2025-12-17  1:15 ` [PATCH] nfc: llcp: stop processing on LLCP_CLOSED in nfc_llcp_recv_hdlc() Qianchang Zhao
2025-12-17  7:35   ` Krzysztof Kozlowski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07e506c9-21f7-4d4a-ada3-ad0004acf6fc@kernel.org \
    --to=krzk@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuzhitong1993@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pioooooooooip@gmail.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox