From: Oliver Hartkopp <socketcan@hartkopp.net>
To: David Hunter <david.hunter.linux@gmail.com>,
mkl@pengutronix.de, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: skhan@linuxfoundation.org, javier.carrasco.cruz@gmail.com
Subject: Re: [PATCH 1/1] Net: bcm.c: Remove Subtree Instead of Entry
Date: Fri, 9 Aug 2024 11:57:41 +0200 [thread overview]
Message-ID: <2bf44b8d-b286-4a94-8e1d-6c4e736a1d07@hartkopp.net> (raw)
In-Reply-To: <20240808202658.5933-1-david.hunter.linux@gmail.com>
Hello David,
many thanks for the patch and the description.
Btw. the data structures of the elements inside that bcm proc dir should
have been removed at that point, so that the can-bcm dir should be empty.
I'm not sure what happens to the open sockets that are (later) removed
in bcm_release() when we use remove_proc_subtree() as suggested.
Removing this warning probably does not heal the root cause of the issue.
What did you do to trigger the warning? Did you work with network
namespaces or LXC/Docker and purged an entire namespace?
Best regards,
Oliver
On 08.08.24 22:26, David Hunter wrote:
> Fix a warning with bcm.c that is caused by removing an entry. If the
> entry had a process as a child, a warning is generated:
>
> remove_proc_entry: removing non-empty directory 'net/can-bcm'...
> WARNING: CPU: 1 PID: 71 at fs/proc/generic.c:717 remove_proc_entry
> Call Trace:
> remove_proc_entry
> canbcm_pernet_exit
> ops_exit_list
>
> Instead of simply removing the entry, remove the entire subdirectory.
> The child process will still be removed, but without a warning occurring.
>
> This patch was compiled and the code traced with gdb to see that the
> tree was removed. The code was run to see that the warning was removed.
> In addition, the code was tested with the kselftest
> net subsystem. No regressions were detected.
>
> Signed-off-by: David Hunter <david.hunter.linux@gmail.com>
> ---
> net/can/bcm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/can/bcm.c b/net/can/bcm.c
> index 27d5fcf0eac9..fea48fd793e5 100644
> --- a/net/can/bcm.c
> +++ b/net/can/bcm.c
> @@ -1779,7 +1779,7 @@ static void canbcm_pernet_exit(struct net *net)
> #if IS_ENABLED(CONFIG_PROC_FS)
> /* remove /proc/net/can-bcm directory */
> if (net->can.bcmproc_dir)
> - remove_proc_entry("can-bcm", net->proc_net);
> + remove_proc_subtree("can-bcm", net->proc_net);
> #endif /* CONFIG_PROC_FS */
> }
>
next prev parent reply other threads:[~2024-08-09 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 20:26 David Hunter
2024-08-09 9:57 ` Oliver Hartkopp [this message]
2024-08-09 16:21 ` David Hunter
2024-08-09 20:22 ` Kuniyuki Iwashima
2024-08-09 20:28 ` Kuniyuki Iwashima
2024-08-30 10:56 ` Marc Kleine-Budde
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=2bf44b8d-b286-4a94-8e1d-6c4e736a1d07@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®