From: "Gaël Blivet" <gael.blivet@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: ChenXiaoSong <chenxiaosong@chenxiaosong.com>,
linux-cifs@vger.kernel.org, smfrench@gmail.com, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com, metze@samba.org,
andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH 0/3] smb/server: fix some bugs in preparation for change notify support
Date: Sun, 19 Jul 2026 01:40:26 +0200 [thread overview]
Message-ID: <70B82D7E-4699-4C9F-A1F3-2B51C61BFD20@gmail.com> (raw)
In-Reply-To: <CAKYAXd8-ZSbyU8NPCBYCVrExRJiRdn=y0mYbc71sSRqD4LoYAw@mail.gmail.com>
I have a draft for the follow-up patch that I am testing but I am not yet satisfied with it as live tests currently show workers being permanently wedged in smb2_notify().
I'll need a bit more time before sending it.
Thanks!
> Le 18 juil. 2026 à 06:51, Namjae Jeon <linkinjeon@kernel.org> a écrit :
>
> I have already merged your patch ("ksmbd: defer CHANGE_NOTIFY
> completion instead of STATUS_NOT_IMPLEMENTED") into the
> ksmbd-for-next-next branch. Please use that as the base and send a
> follow-up patches to update the implementation using the
> approach you and ChenXiaoSong discussed.
next prev parent reply other threads:[~2026-07-18 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 13:55 [PATCH 0/3] smb/server: fix some bugs in preparation for change notify support ChenXiaoSong
2026-07-15 13:55 ` [PATCH 1/3] smb/server: fix signing when a response uses more than one iov ChenXiaoSong
2026-07-15 14:25 ` Andy Shevchenko
2026-07-15 15:04 ` ChenXiaoSong
2026-07-15 15:18 ` ChenXiaoSong
2026-07-15 13:55 ` [PATCH 2/3] smb/server: cancel async requests when closing connection ChenXiaoSong
2026-07-15 14:26 ` Andy Shevchenko
2026-07-15 13:55 ` [PATCH 3/3] smb/server: stop new async work " ChenXiaoSong
2026-07-15 15:22 ` [PATCH 0/3] smb/server: fix some bugs in preparation for change notify support ChenXiaoSong
2026-07-18 4:51 ` Namjae Jeon
2026-07-18 23:40 ` Gaël Blivet [this message]
2026-07-19 1:28 ` 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=70B82D7E-4699-4C9F-A1F3-2B51C61BFD20@gmail.com \
--to=gael.blivet@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.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