Linux CAN drivers development
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Davide Caratti <dcaratti@redhat.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH] can: add protocol counter for AF_CAN sockets
Date: Sun, 16 Mar 2025 13:36:40 +0100	[thread overview]
Message-ID: <78951192-82b1-45bc-9903-d314c94cd182@hartkopp.net> (raw)
In-Reply-To: <9db5d0e6c11b232ad895885616f1258882a32f61.1741952160.git.dcaratti@redhat.com>

Hello Davide,

thanks for your patch!

~/linux/net/can$ git grep sock_put .
af_can.c:               sock_put(sk);
af_can.c:               sock_put(sk);
bcm.c:  sock_put(sk);
isotp.c:        sock_put(sk);
j1939/socket.c: sock_put(sk);
j1939/transport.c:      sock_put(session->sk);
raw.c:  sock_put(sk);

But don't we need to take care on every place where sock_put() is called 
where sock_prot_inuse_add() has to decrease the counter?

Best regards,
Oliver

On 14.03.25 12:39, Davide Caratti wrote:
> The third column in the output of the following command:
> 
>   # grep CAN /proc/net/protocols
> 
> is systematically '0': use sock_prot_inuse_add() to account for the number
> of sockets for each protocol on top of AF_CAN family.
> 
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
> ---
>   net/can/af_can.c | 2 ++
>   net/can/bcm.c    | 1 +
>   net/can/isotp.c  | 1 +
>   net/can/raw.c    | 5 ++++-
>   4 files changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/net/can/af_can.c b/net/can/af_can.c
> index 01f3fbb3b67d..7b191dbe3693 100644
> --- a/net/can/af_can.c
> +++ b/net/can/af_can.c
> @@ -172,6 +172,8 @@ static int can_create(struct net *net, struct socket *sock, int protocol,
>   		sock_orphan(sk);
>   		sock_put(sk);
>   		sock->sk = NULL;
> +	} else {
> +		sock_prot_inuse_add(net, sk->sk_prot, 1);
>   	}
>   
>    errout:
> diff --git a/net/can/bcm.c b/net/can/bcm.c
> index 217049fa496e..6dc041e054ba 100644
> --- a/net/can/bcm.c
> +++ b/net/can/bcm.c
> @@ -1625,6 +1625,7 @@ static int bcm_release(struct socket *sock)
>   	sock->sk = NULL;
>   
>   	release_sock(sk);
> +	sock_prot_inuse_add(net, sk->sk_prot, -1);
>   	sock_put(sk);
>   
>   	return 0;
> diff --git a/net/can/isotp.c b/net/can/isotp.c
> index 16046931542a..789583c62f98 100644
> --- a/net/can/isotp.c
> +++ b/net/can/isotp.c
> @@ -1239,6 +1239,7 @@ static int isotp_release(struct socket *sock)
>   	sock->sk = NULL;
>   
>   	release_sock(sk);
> +	sock_prot_inuse_add(net, sk->sk_prot, -1);
>   	sock_put(sk);
>   
>   	return 0;
> diff --git a/net/can/raw.c b/net/can/raw.c
> index 9b1d5f036f57..020f21430b1d 100644
> --- a/net/can/raw.c
> +++ b/net/can/raw.c
> @@ -397,11 +397,13 @@ static int raw_release(struct socket *sock)
>   {
>   	struct sock *sk = sock->sk;
>   	struct raw_sock *ro;
> +	struct net *net;
>   
>   	if (!sk)
>   		return 0;
>   
>   	ro = raw_sk(sk);
> +	net = sock_net(sk);
>   
>   	spin_lock(&raw_notifier_lock);
>   	while (raw_busy_notifier == ro) {
> @@ -421,7 +423,7 @@ static int raw_release(struct socket *sock)
>   			raw_disable_allfilters(dev_net(ro->dev), ro->dev, sk);
>   			netdev_put(ro->dev, &ro->dev_tracker);
>   		} else {
> -			raw_disable_allfilters(sock_net(sk), NULL, sk);
> +			raw_disable_allfilters(net, NULL, sk);
>   		}
>   	}
>   
> @@ -440,6 +442,7 @@ static int raw_release(struct socket *sock)
>   	release_sock(sk);
>   	rtnl_unlock();
>   
> +	sock_prot_inuse_add(net, sk->sk_prot, -1);
>   	sock_put(sk);
>   
>   	return 0;


  parent reply	other threads:[~2025-03-16 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14 11:39 [PATCH] can: add protocol counter for AF_CAN sockets Davide Caratti
2025-03-14 12:31 ` Marc Kleine-Budde
2025-03-16 12:39   ` Oliver Hartkopp
2025-03-17  9:20     ` Marc Kleine-Budde
2025-03-17 10:14       ` Oliver Hartkopp
2025-03-16 12:36 ` Oliver Hartkopp [this message]
2025-03-17 10:14   ` Davide Caratti
2025-03-17 10:21     ` Oliver Hartkopp
2025-03-17 15:50       ` Davide Caratti
2025-03-18 13:01         ` Oliver Hartkopp

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=78951192-82b1-45bc-9903-d314c94cd182@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=dcaratti@redhat.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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