From: Steve French <smfrench@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: [GIT PULL] ksmbd server fixes
Date: Fri, 24 Oct 2025 20:10:57 -0500 [thread overview]
Message-ID: <CAH2r5muFRm0X_uYTFySHj-T7YZQhXZWVa4WzKny_YmEzXOhCBw@mail.gmail.com> (raw)
Please pull the following changes since commit
211ddde0823f1442e4ad052a2f30f050145ccada:
Linux 6.18-rc2 (2025-10-19 15:19:16 -1000)
are available in the Git repository at:
git://git.samba.org/ksmbd.git tags/v6.18-rc2-smb-server-fixes
for you to fetch changes up to dd6940f5c7dbee7ae70708f4c8967c3c8cb1d965:
smb: server: let free_transport() wait for
SMBDIRECT_SOCKET_DISCONNECTED (2025-10-23 20:58:51 -0500)
----------------------------------------------------------------
Seven ksmbd server smbdirect (RDMA) fixes in order avoid potential
submission queue overflows
- free transport teardown fix
- six credit related fixes (five server related, one client related)
----------------------------------------------------------------
Stefan Metzmacher (7):
smb: server: allocate enough space for RW WRs and ib_drain_qp()
smb: smbdirect: introduce smbdirect_socket.send_io.lcredits.*
smb: server: smb_direct_disconnect_rdma_connection() already
wakes all waiters on error
smb: server: simplify sibling_list handling in
smb_direct_flush_send_list/send_done
smb: server: make use of smbdirect_socket.send_io.lcredits.*
smb: client: make use of smbdirect_socket.send_io.lcredits.*
smb: server: let free_transport() wait for SMBDIRECT_SOCKET_DISCONNECTED
fs/smb/client/smbdirect.c | 67 +++--
fs/smb/common/smbdirect/smbdirect_socket.h | 13 +-
fs/smb/server/transport_rdma.c | 344 +++++++++++++++---------
3 files changed, 273 insertions(+), 151 deletions(-)
--
Thanks,
Steve
next reply other threads:[~2025-10-25 1:11 UTC|newest]
Thread overview: 166+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 1:10 Steve French [this message]
2025-10-25 2:02 ` [GIT PULL] ksmbd server fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-11-13 4:39 Steve French
2025-11-13 13:04 ` pr-tracker-bot
2025-11-07 2:41 Steve French
2025-11-07 16:05 ` pr-tracker-bot
2025-10-28 23:50 Steve French
2025-10-29 1:03 ` pr-tracker-bot
2025-10-16 16:52 Steve French
2025-10-16 18:06 ` pr-tracker-bot
2025-10-02 17:20 Steve French
2025-10-03 21:31 ` pr-tracker-bot
2025-09-24 2:21 Steve French
2025-09-24 19:23 ` pr-tracker-bot
2025-09-18 0:24 Steve French
2025-09-18 3:38 ` pr-tracker-bot
2025-08-21 2:02 Steve French
2025-08-21 12:01 ` pr-tracker-bot
2025-08-08 4:58 Steve French
2025-08-09 5:19 ` pr-tracker-bot
2025-07-11 13:21 Steve French
2025-07-12 18:15 ` pr-tracker-bot
2025-06-18 22:46 Steve French
2025-06-19 0:52 ` pr-tracker-bot
2025-05-23 15:23 Steve French
2025-05-23 16:51 ` pr-tracker-bot
2025-05-08 3:34 Steve French
2025-05-08 15:46 ` pr-tracker-bot
2025-04-28 23:44 Steve French
2025-04-29 0:08 ` pr-tracker-bot
2025-04-18 16:24 Steve French
2025-04-18 16:46 ` pr-tracker-bot
2025-04-03 23:13 Steve French
2025-04-03 23:24 ` pr-tracker-bot
2025-03-15 1:55 Steve French
2025-03-15 4:49 ` pr-tracker-bot
2025-01-22 23:51 Steve French
2025-01-24 1:10 ` pr-tracker-bot
2025-01-10 0:37 Steve French
2025-01-10 2:25 ` pr-tracker-bot
2024-12-18 23:40 Steve French
2024-12-19 17:03 ` pr-tracker-bot
2024-12-12 23:47 Steve French
2024-12-13 5:00 ` pr-tracker-bot
2024-12-05 16:17 Steve French
2024-12-05 23:08 ` pr-tracker-bot
2024-11-28 22:32 Steve French
2024-11-30 18:39 ` pr-tracker-bot
2024-11-08 22:29 Steve French
2024-11-08 23:25 ` pr-tracker-bot
2024-10-16 6:09 Steve French
2024-10-16 20:51 ` pr-tracker-bot
2024-10-03 16:29 Steve French
2024-10-03 16:53 ` pr-tracker-bot
2024-09-28 2:05 Steve French
2024-09-28 16:45 ` pr-tracker-bot
2024-09-17 6:23 Steve French
2024-09-19 5:20 ` pr-tracker-bot
2024-09-04 14:55 Steve French
2024-09-04 16:46 ` pr-tracker-bot
2024-08-24 13:35 Steve French
2024-08-25 0:22 ` pr-tracker-bot
2024-08-20 23:53 Steve French
2024-08-21 2:07 ` pr-tracker-bot
2024-08-13 2:57 Steve French
2024-08-13 16:17 ` pr-tracker-bot
2024-07-21 23:55 Steve French
2024-07-22 3:54 ` pr-tracker-bot
2024-07-09 14:57 Steve French
2024-07-09 15:21 ` pr-tracker-bot
2024-06-15 15:45 Steve French
2024-06-15 19:15 ` pr-tracker-bot
2024-05-25 3:16 Steve French
2024-05-25 21:32 ` pr-tracker-bot
2024-04-22 23:20 Steve French
2024-04-22 23:51 ` pr-tracker-bot
2024-04-05 3:15 Steve French
2024-04-05 17:09 ` pr-tracker-bot
2024-02-10 1:45 Steve French
2024-02-10 16:26 ` pr-tracker-bot
2024-01-27 7:20 Steve French
2024-01-27 17:21 ` pr-tracker-bot
2024-01-18 0:39 Steve French
2024-01-19 18:03 ` pr-tracker-bot
2024-01-11 14:20 Steve French
2024-01-12 5:07 ` pr-tracker-bot
2023-11-27 21:00 Steve French
2023-11-28 1:26 ` pr-tracker-bot
2023-11-10 7:16 Steve French
2023-11-10 18:47 ` pr-tracker-bot
2023-11-02 2:46 Steve French
2023-11-02 18:38 ` pr-tracker-bot
2023-10-15 2:46 Steve French
2023-10-15 2:52 ` pr-tracker-bot
2023-10-08 4:27 Steve French
2023-10-08 18:06 ` pr-tracker-bot
2023-09-29 22:11 Steve French
2023-09-29 23:59 ` pr-tracker-bot
2023-09-17 1:55 Steve French
2023-09-17 18:24 ` pr-tracker-bot
2023-08-09 23:11 Steve French
2023-08-10 5:02 ` pr-tracker-bot
2023-07-26 6:17 Steve French
2023-07-26 18:42 ` pr-tracker-bot
2023-06-30 5:59 Steve French
2023-07-01 5:04 ` pr-tracker-bot
2023-06-20 4:45 Steve French
2023-06-20 19:01 ` pr-tracker-bot
2023-06-11 1:59 Steve French
2023-06-11 17:43 ` pr-tracker-bot
2023-05-21 5:14 Steve French
2023-05-21 18:06 ` Linus Torvalds
2023-05-21 18:32 ` Linus Torvalds
2023-05-21 19:03 ` Steve French
2023-05-21 19:21 ` Linus Torvalds
2023-05-22 4:38 ` Steve French
2023-05-22 8:04 ` ronnie sahlberg
2023-05-21 18:09 ` pr-tracker-bot
2023-05-06 0:19 Steve French
2023-05-06 2:20 ` pr-tracker-bot
2023-04-27 2:11 Steve French
2023-04-29 18:19 ` pr-tracker-bot
2023-04-07 4:16 Steve French
2023-04-07 20:56 ` pr-tracker-bot
2023-03-25 0:00 Steve French
2023-03-25 1:18 ` pr-tracker-bot
2023-02-22 4:15 Steve French
2023-02-22 22:26 ` pr-tracker-bot
2023-01-28 1:45 Steve French
2023-01-28 19:33 ` pr-tracker-bot
2023-01-10 3:13 Steve French
2023-01-10 11:36 ` pr-tracker-bot
2022-12-15 3:18 Steve French
2022-12-15 17:32 ` Linus Torvalds
2022-12-15 18:28 ` pr-tracker-bot
2022-10-06 23:53 Steve French
2022-10-07 17:00 ` pr-tracker-bot
2022-08-19 5:03 Steve French
2022-08-19 21:14 ` pr-tracker-bot
2022-08-08 20:00 Steve French
2022-08-09 3:20 ` pr-tracker-bot
2022-06-28 22:07 Steve French
2022-06-29 16:44 ` pr-tracker-bot
2022-06-01 6:20 Steve French
2022-06-01 19:34 ` pr-tracker-bot
2022-04-24 0:10 Steve French
2022-04-24 0:32 ` pr-tracker-bot
2022-04-01 18:40 Steve French
2022-04-01 21:41 ` Linus Torvalds
2022-04-01 21:45 ` pr-tracker-bot
2022-03-29 1:39 Steve French
2022-03-30 1:48 ` Linus Torvalds
2022-03-30 1:57 ` Steve French
2022-03-30 2:23 ` Linus Torvalds
2022-03-30 9:18 ` Christoph Hellwig
2022-03-30 9:17 ` Christoph Hellwig
2022-04-01 1:20 ` Al Viro
2022-04-01 12:52 ` Namjae Jeon
2022-04-01 13:34 ` Al Viro
2022-04-01 14:58 ` Namjae Jeon
2022-02-07 21:04 Steve French
2022-02-07 23:34 ` pr-tracker-bot
2021-11-27 21:43 Steve French
2021-11-27 22:52 ` pr-tracker-bot
2021-09-26 12:13 Steve French
2021-09-26 21:11 ` pr-tracker-bot
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=CAH2r5muFRm0X_uYTFySHj-T7YZQhXZWVa4WzKny_YmEzXOhCBw@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).