Re: [PATCH 1/2] Separate target visibility from reaped state information

Looks good: Reviewed-by: Christoph Hellwig A few things I noticed when looking over this and the previous iterations, which are more notes for future work than an actual comment on this patch: - what lock protects ->visible and ->reaped (or previously ->state)? It seems like

[PATCH 1/2] Separate target visibility from reaped state information

Instead of representing the states "visible in sysfs" and "has been removed from the target list" by a single state variable, use two variables to represent this information. Signed-off-by: Bart Van Assche Cc: Johannes Thumshirn Cc: Christoph