Skip to content

rbd: only set up Linux files for mapped devices

Alex Elder ceph-devel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest5 patches 3 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5rbd: drop module laterdrivers/block/rbd.c+1 -30 replies
2/5rbd: don't destroy rbd_dev in device release functiondrivers/block/rbd.c+0 -00 replies
3/5rbd: define rbd_dev_unprobe()drivers/block/rbd.c+0 -02 replies
4/5rbd: don't have device release destroy rbd_devdrivers/block/rbd.c+0 -20 replies
5/5rbd: set up devices only for mapped imagesdrivers/block/rbd.c+0 -00 replies

Reviews trailers per patch

1 of 5 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchJosh Durgin
SeriesR-b
1/5
2/5
3/5R-b
4/5
5/5

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/5] rbd: only set up Linux files for mapped devices

This series does a few more things to separate the ceph and Linux side of rbd device initialization, and to make sure things get cleaned up in a sane way when errors occur. The last patch makes it so only the rbd image getting mapped has Linux device and sysfs stuff associated with them. The parent rbd devices for layered images never needed this stuff, and things have now been rearranged such that we can do away with that.

These patches are available in the ceph-client git repository in the branch "review/wip-rbd-cleanup-5".

-Alex
[PATCH 1/5] rbd: drop module later
[PATCH 2/5] rbd: don't destroy rbd_dev in device release function [PATCH 3/5] rbd: define rbd_dev_unprobe()
[PATCH 4/5] rbd: don't have device release destroy rbd_dev [PATCH 5/5] rbd: set up devices only for mapped images