[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4df016bc-570c-d166-47dd-36a9f21fad13@suse.de>
Date: Fri, 21 Aug 2020 11:26:19 +0200
From: Hannes Reinecke <hare@...e.de>
To: Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>
Cc: Justin Sanders <justin@...aid.com>,
Josef Bacik <josef@...icpanda.com>,
Xianting Tian <xianting_tian@....com>,
linux-block@...r.kernel.org, dm-devel@...hat.com,
Stefan Haberland <sth@...ux.ibm.com>,
Jan Hoeppner <hoeppner@...ux.ibm.com>,
linux-kernel@...r.kernel.org, nbd@...er.debian.org,
linux-nvme@...ts.infradead.org, linux-s390@...r.kernel.org
Subject: Re: [PATCH 2/2] block: fix locking for struct block_device size
updates
On 8/21/20 10:56 AM, Christoph Hellwig wrote:
> Two different callers use two different mutexes for updating the
> block device size, which obviously doesn't help to actually protect
> against concurrent updates from the different callers. In addition
> one of the locks, bd_mutex is rather prone to deadlocks with other
> parts of the block stack that use it for high level synchronization.
>
> Switch to using a new spinlock protecting just the size updates, as
> that is all we need, and make sure everyone does the update through
> the proper helper.
>
> This fixeѕ a bug reported with the nvme revalidating disks during a
> hot removal operation.
>
> Reported-by: Xianting Tian <xianting_tian@....com>
> Signed-off-by: Christoph Hellwig <hch@....de>
> ---
> block/partitions/core.c | 4 ++--
> drivers/block/aoe/aoecmd.c | 4 +---
> drivers/md/dm.c | 15 ++-------------
> drivers/s390/block/dasd_ioctl.c | 9 ++-------
> fs/block_dev.c | 18 +++++++++---------
> include/linux/blk_types.h | 1 +
> 6 files changed, 17 insertions(+), 34 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@...e.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
Powered by blists - more mailing lists