From: Stefan Metzmacher <metze@samba.org>
To: linux-cifs@vger.kernel.org, samba-technical@lists.samba.org
Cc: metze@samba.org, Namjae Jeon <linkinjeon@kernel.org>,
Steve French <smfrench@gmail.com>, Tom Talpey <tom@talpey.com>
Subject: [PATCH 0/4] smb:server: fix possible use after free problems
Date: Mon, 4 Aug 2025 14:15:49 +0200 [thread overview]
Message-ID: <cover.1754309565.git.metze@samba.org> (raw)
While refactoring the client and server smbdirect code I
noticed a few problems where we might hit use after free
style problems.
In order to allow backports I decided to fix the problems
before trying to move things to common code.
The client has similar problems, I've sent a separate
patchset for the client already.
Stefan Metzmacher (4):
smb: server: remove separate empty_recvmsg_queue
smb: server: make sure we call ib_dma_unmap_single() only if we called
ib_dma_map_single already
smb: server: let recv_done() consitently call
put_recvmsg/smb_direct_disconnect_rdma_connection
smb: server: let recv_done() avoid touching data_transfer after
cleanup/move
fs/smb/server/transport_rdma.c | 97 ++++++++++++----------------------
1 file changed, 35 insertions(+), 62 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-04 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 12:15 Stefan Metzmacher [this message]
2025-08-04 12:15 ` [PATCH 1/4] smb: server: remove separate empty_recvmsg_queue Stefan Metzmacher
2025-08-04 12:15 ` [PATCH 2/4] smb: server: make sure we call ib_dma_unmap_single() only if we called ib_dma_map_single already Stefan Metzmacher
2025-08-04 12:15 ` [PATCH 3/4] smb: server: let recv_done() consitently call put_recvmsg/smb_direct_disconnect_rdma_connection Stefan Metzmacher
2025-08-04 12:15 ` [PATCH 4/4] smb: server: let recv_done() avoid touching data_transfer after cleanup/move Stefan Metzmacher
2025-08-05 8:48 ` [PATCH 0/4] smb:server: fix possible use after free problems Namjae Jeon
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=cover.1754309565.git.metze@samba.org \
--to=metze@samba.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.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;
as well as URLs for NNTP newsgroup(s).