dm: Avoid use-after-free of a mapped device
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 3 repliesIn review
- v12 patches 10 repliesSuperseded
Changes in v2 from the cover letter
- Invoking blk_run_queue() again guarantees that the queue will be run sooner or later.
- Refined patch descriptions and source code comments.
- Left out the "Cc: <[email protected]>" tags.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | block: Convert blk_run_queue() recursion into iterationblock/ include/ | +25 | 0 replies | |
| 2/2 | dm: Avoid running the md queue after the last dm_put()drivers/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/2] dm: Avoid use-after-free of a mapped device
This mini-series of two patches avoids that the device mapper implementation can trigger a use-after-free during removal of a mapped device. The two patches in this series are:
- block: Convert blk_run_queue() recursion into iteration.
- dm: Avoid running the md queue after the last dm_put().
Note: these patches are the result of source reading. As far as I know this issue has not (yet) caused any harm.
Changes compared to v1:
- Invoking blk_run_queue() again guarantees that the queue will be run sooner or later.
- Refined patch descriptions and source code comments.
- Left out the "Cc: <[email protected]>" tags.