From: chenxiaosong.chenxiaosong@linux.dev
To: smfrench@gmail.com, linkinjeon@kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com
Cc: linux-cifs@vger.kernel.org, ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: [PATCH v2 0/1] smb/server: fix some refcount leaks
Date: Mon, 29 Dec 2025 11:15:17 +0800 [thread overview]
Message-ID: <20251229031518.1027240-1-chenxiaosong.chenxiaosong@linux.dev> (raw)
From: ChenXiaoSong <chenxiaosong@kylinos.cn>
v1: https://lore.kernel.org/linux-cifs/20251229021330.1026506-1-chenxiaosong.chenxiaosong@linux.dev/
v1->v2:
- Call ksmbd_put_durable_fd() immediately after ksmbd_vfs_getattr() has completed.
The following patches from v1 have already been merged into ksmbd.git ksmbd-for-next-next:
- 0d762babd1db smb/server: fix refcount leak in parse_durable_handle_context()
My dear team member, ZhangGuoDong, has caught some refcount leak issues.
Other patches pending review (including those from others) can be found at the following link:
https://chenxiaosong.com/en/smb-patch.html
ZhangGuoDong (1):
smb/server: fix refcount leak in smb2_open()
fs/smb/server/smb2pdu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2025-12-29 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 3:15 chenxiaosong.chenxiaosong [this message]
2025-12-29 3:15 ` [PATCH v2 1/1] smb/server: fix refcount leak in smb2_open() chenxiaosong.chenxiaosong
2025-12-29 4:06 ` Namjae Jeon
2026-02-25 16:49 ` Guenter Roeck
2026-02-26 4:12 ` ChenXiaoSong
2026-02-26 4:27 ` Guenter Roeck
2026-02-26 5:09 ` Guenter Roeck
2026-02-27 4:07 ` ChenXiaoSong
2026-02-27 4:12 ` ChenXiaoSong
2026-02-27 4:43 ` Namjae Jeon
2026-02-27 4:42 ` Guenter Roeck
2026-02-27 4:53 ` ChenXiaoSong
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=20251229031518.1027240-1-chenxiaosong.chenxiaosong@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.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