Re: fix block device size update serialization v2

On 8/27/20 1:47 AM, Christoph Hellwig wrote: > Jens, can you consider this for 5.9? It reliably fixes the reported > hangs with nvme hotremoval that we've had for a few releases. I've queued this up for 5.10. I think it's too late for 5.9 at this point, and it's not a regression in this release.

Re: fix block device size update serialization v2

Jens, can you consider this for 5.9? It reliably fixes the reported hangs with nvme hotremoval that we've had for a few releases. On Sun, Aug 23, 2020 at 11:10:40AM +0200, Christoph Hellwig wrote: > Hi Jens, > > this series fixes how we update i_size for the block device inodes (and > thus the b

fix block device size update serialization v2

Hi Jens, this series fixes how we update i_size for the block device inodes (and thus the block device). Different helpers use two different locks (bd_mutex and i_rwsem) to protect the update, and it appears device mapper uses yet another internal lock. A lot of the drivers do the update handcra

fix block device size update serialization

Hi Jens, this series fixes how we update i_size for the block device inodes (and thus the block device). Different helpers use two different locks (bd_mutex and i_rwsem) to protect the update, and it appears device mapper uses yet another internal lock. A lot of the drivers do the update handcra