Bug 14449 - We should not cancel async state changing operations when a single connection is disconnected in order to have a correct replay behavior
Summary: We should not cancel async state changing operations when a single connection...
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.13.0.rc1
Hardware: All All
: P5 critical (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks: 13703 14534
  Show dependency tree / graph
 
Reported: 2020-07-24 16:02 UTC by Stefan Metzmacher
Modified: 2020-10-14 13:02 UTC (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Metzmacher 2020-07-24 16:02:32 UTC 
Currently we cancel any pending operation on a disconnecting connection,
even it's not the last connection (with multi-channel).

If an unfinished open waits for an oplock break, it
should be possible to resume that operation on new channel.
Comment 1 Stefan Metzmacher 2020-07-24 16:04:43 UTC 
Mark as regression in order to remember it for 4.13.0 if possible
Comment 2 Stefan Metzmacher 2020-08-26 12:22:06 UTC 
Replays on pending creates should return FILE_NOT_AVAILABLE?