On Tue, Mar 03, 2015 at 09:49:45PM +0900, Sergey Senozhatsky wrote:
> Device reset currently consists of two steps:
> a) holding ->bd_mutex we ensure that there are no device users
> (bdev->bd_openers)
>
> b) and internal part (executed under bdev->bd_mutex and partially
> under zram->init_lock)
On Tue, Mar 03, 2015 at 09:49:45PM +0900, Sergey Senozhatsky wrote:
Device reset currently consists of two steps:
a) holding -bd_mutex we ensure that there are no device users
(bdev-bd_openers)
b) and internal part (executed under bdev-bd_mutex and partially
under zram-init_lock) that
Device reset currently consists of two steps:
a) holding ->bd_mutex we ensure that there are no device users
(bdev->bd_openers)
b) and internal part (executed under bdev->bd_mutex and partially
under zram->init_lock) that resets the device - frees allocated
memory and returns the device back to
Device reset currently consists of two steps:
a) holding -bd_mutex we ensure that there are no device users
(bdev-bd_openers)
b) and internal part (executed under bdev-bd_mutex and partially
under zram-init_lock) that resets the device - frees allocated
memory and returns the device back to its
Device reset currently consists of two steps:
a) holding ->bd_mutex we ensure that there are no device users
(bdev->bd_openers)
b) and internal part (executed under bdev->bd_mutex and partially
under zram->init_lock) that resets the device - frees allocated
memory and returns the device back to
Device reset currently consists of two steps:
a) holding -bd_mutex we ensure that there are no device users
(bdev-bd_openers)
b) and internal part (executed under bdev-bd_mutex and partially
under zram-init_lock) that resets the device - frees allocated
memory and returns the device back to its
6 matches
Mail list logo