Re: [PATCH v2 0/3] smb/server: improve async interim response handling for compound requests
Namjae Jeon <[email protected]>
| Newsgroups | org.kernel.vger.linux-cifs |
|---|---|
| Message-ID | <CAKYAXd_1Emq0LhBQJtvWkPU+EkaQ6_3UmBxQogTcDau4tBpBrw@mail.gmail.com> |
On Wed, Jul 8, 2026 at 11:56 AM ChenXiaoSong <[email protected]> wrote: > > From: ChenXiaoSong <[email protected]> > > v1->v2: send compound prefix before async pending response, > then send STATUS_PENDING as a standalone response. > > v1: https://lore.kernel.org/linux-cifs/[email protected]/ > > I am currently implementing the ksmbd change notify feature, and I have > encountered the following issue. > > Before this patchset, no CREATE response: > > Windows client compound request: > CREATE dir; CHANGE_NOTIFY, fid = compound fid > > Server response: > CHANGE_NOTIFY STATUS_PENDING, AsyncId = N > > After this patchset: > > Server response: > CREATE dir SUCCESS, fid = X > CHANGE_NOTIFY STATUS_PENDING, AsyncId = N > > ChenXiaoSong (3): > smb/server: send compound prefix before async pending response > smb/server: introduce struct ksmbd_transport_write > smb/server: use MSG_EOR for async interim response Applied them to #ksmbd-for-next-next. Thanks!