Bug #63734
closedclient: handle callback when async io fails
0%
Description
There are several cases where the async call might experience some failure and the helper functions would just return an errno but there's no code path taking care of the context completion. I experienced these issues while running [0] locally, created few trackers and started addressing them in separate PRs but soon realised that it was quite unnecessary to do, therefore I moved all the commits into a single PR; since it would be cumbersome to manage all those trackers and their backports, i'm creating this (parent) tracker.
[0] https://github.com/ceph/ceph/pull/54435
*async io failure tracker
https://tracker.ceph.com/issues/63632
https://tracker.ceph.com/issues/63648
https://tracker.ceph.com/issues/63629
https://tracker.ceph.com/issues/63619
https://tracker.ceph.com/issues/63679
Updated by Dhairya Parmar 5 months ago
- Related to Bug #63632: client: fh obtained using O_PATH can stall the caller during async I/O added
Updated by Dhairya Parmar 5 months ago
- Related to Bug #63648: client: ensure callback is finished if write fails during async I/O added
Updated by Dhairya Parmar 5 months ago
- Related to Bug #63629: client: handle context completion during async I/O call when the client is not mounting added
Updated by Dhairya Parmar 5 months ago
- Related to Bug #63619: client: check for negative value of iovcnt before passing it to internal functions during async I/O added
Updated by Dhairya Parmar 5 months ago
- Related to Bug #63679: client: handle zero byte sync/async write cases added
Updated by Venky Shankar 3 months ago
- Status changed from In Progress to Resolved
Dhairya, this doesn't need backport IMO. Would you concur?