public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DaeMyung Kang <charsyam@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>, Steve French <smfrench@gmail.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Tom Talpey <tom@talpey.com>, Hyunchul Lee <hyc.lee@gmail.com>,
	Bahubali B Gumaji <bahubali.bg@samsung.com>,
	Sang-Soo Lee <constant.lee@samsung.com>,
	linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
	DaeMyung Kang <charsyam@gmail.com>
Subject: [PATCH] ksmbd: stop transports before procfs cleanup during shutdown
Date: Tue, 28 Apr 2026 22:38:16 +0900	[thread overview]
Message-ID: <20260428133816.922544-1-charsyam@gmail.com> (raw)

ksmbd_server_shutdown() removes the whole /proc/fs/ksmbd subtree via
ksmbd_proc_cleanup() before ksmbd_conn_transport_destroy() runs.  The
transport teardown later calls delete_proc_clients(), which removes the
cached proc_clients entry under that subtree.

Since proc_remove(ksmbd_proc_fs) already removes the subtree, that later
proc_remove(proc_clients) can operate on a freed proc_dir_entry and trip
KASAN during rmmod:

  BUG: KASAN: slab-use-after-free in proc_remove
  proc_remove
  ksmbd_conn_transport_destroy
  ksmbd_server_exit

Keep the control sysfs class unregistered before tearing down transports
so kill_server cannot race a module-exit cleanup, but stop the transports
before removing the root procfs subtree.  That lets client and session
proc entries be removed while their parent is still alive, then
ksmbd_proc_cleanup() can remove the remaining root entries.

KASAN testing confirms the ordering issue: the pre-fix module
reproduces the proc_remove slab-use-after-free during rmmod, while the
patched module passes the same rmmod scenario.  Active pending-IO
testing also passes; the observed workqueue hog warning is present on
the pre-fix baseline as well and is not introduced by this shutdown
ordering change.

Fixes: b38f99c1217a ("ksmbd: add procfs interface for runtime monitoring and statistics")
Signed-off-by: DaeMyung Kang <charsyam@gmail.com>
---
 fs/smb/server/server.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/smb/server/server.c b/fs/smb/server/server.c
index 5d799b2d4c62..188a6a72f7fa 100644
--- a/fs/smb/server/server.c
+++ b/fs/smb/server/server.c
@@ -535,11 +535,11 @@ static int ksmbd_server_shutdown(void)
 {
 	WRITE_ONCE(server_conf.state, SERVER_STATE_SHUTTING_DOWN);
 
-	ksmbd_proc_cleanup();
 	class_unregister(&ksmbd_control_class);
+	ksmbd_conn_transport_destroy();
+	ksmbd_proc_cleanup();
 	ksmbd_workqueue_destroy();
 	ksmbd_ipc_release();
-	ksmbd_conn_transport_destroy();
 	ksmbd_crypto_destroy();
 	ksmbd_free_global_file_table();
 	destroy_lease_table(NULL);
-- 
2.43.0

                 reply	other threads:[~2026-04-28 13:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260428133816.922544-1-charsyam@gmail.com \
    --to=charsyam@gmail.com \
    --cc=bahubali.bg@samsung.com \
    --cc=constant.lee@samsung.com \
    --cc=hyc.lee@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=senozhatsky@chromium.org \
    --cc=smfrench@gmail.com \
    --cc=tom@talpey.com \
    /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