ublk: fail to start/recover/del device if interrupted by signal
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 3 repliesApplied
- v11 patch 2 repliesSuperseded
Changes in v2 from the cover letter
- add patch 2&3, as reported by Stefano
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ublk: fail to start device if queue setup is interrupteddrivers/ | +2 | 0 replies | |
| 2/3 | ublk: fail to recover device if queue setup is interrupteddrivers/ | +3 | 1 reply | |
| 3/3 | ublk: return -EINTR if breaking from waiting for existed users in DEL_DEVdrivers/ | +2 | 1 reply |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Stefano Garzarella |
|---|---|
| 1/3 | |
| 2/3 | R-b |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH V2 0/3] ublk: fail to start/recover/del device if interrupted by signal
Hi
The 1st & 2nd patch fixes kernel oops if user interrupts the current ublk task.
The 3rd patch returns -EINTR if user interrupts the device deletion.
V2:
- add patch 2&3, as reported by Stefano
Ming Lei (3):
ublk: fail to start device if queue setup is interrupted
ublk: fail to recover device if queue setup is interrupted
ublk: return -EINTR if breaking from waiting for existed users in
DEL_DEV
drivers/block/ublk_drv.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
Signature · 1 line
2.40.1