Re: [PATCH] fs/block_dev.c: Use hd_part to find block inodes

On Fri, 22 Aug 2014, Keith Busch wrote: On Fri, 22 Aug 2014, Christoph Hellwig wrote: On Fri, Aug 22, 2014 at 10:28:16AM -0600, Keith Busch wrote: When using the GENHD_FL_EXT_DEVT disk flags, a newly added device may be assigned the same major/minor as one that was previously removed but opened

Re: [PATCH] fs/block_dev.c: Use hd_part to find block inodes

On Fri, 22 Aug 2014, Christoph Hellwig wrote: On Fri, Aug 22, 2014 at 10:28:16AM -0600, Keith Busch wrote: When using the GENHD_FL_EXT_DEVT disk flags, a newly added device may be assigned the same major/minor as one that was previously removed but opened, and the pesky userspace refuses to clos

Re: [PATCH] fs/block_dev.c: Use hd_part to find block inodes

On Fri, Aug 22, 2014 at 10:28:16AM -0600, Keith Busch wrote: > When using the GENHD_FL_EXT_DEVT disk flags, a newly added device may > be assigned the same major/minor as one that was previously removed but > opened, and the pesky userspace refuses to close it! Which means life time rules for thos

[PATCH] fs/block_dev.c: Use hd_part to find block inodes

When using the GENHD_FL_EXT_DEVT disk flags, a newly added device may be assigned the same major/minor as one that was previously removed but opened, and the pesky userspace refuses to close it! The inode for the old block_device is still open, and so bdget() finds the stale device instead of alloc