Re: [PATCH v2 4/6] ksmbd: defer CHANGE_NOTIFY completion instead of STATUS_NOT_IMPLEMENTED
Gaël Blivet <[email protected]>
| Newsgroups | org.kernel.vger.linux-cifs |
|---|---|
| Message-ID | <[email protected]> |
We can keep that in mind and see in practice how it performs (for example with Time Machine, that can open long-running watches). > Le 10 juil. 2026 à 11:15, ChenXiaoSong <[email protected]> a écrit : > > Yes, before the cancel response or event notification response is sent, the notify request has not completed yet, so the worker will remain waiting. > > If you find that this approach causes any issues, we can refactor it and use a better solution.