From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Yang Yang <yang.yang@vivo.com>
Subject: Re: block: del_gendisk() vs blk_queue_enter() race condition
Date: Tue, 8 Oct 2024 14:31:00 +0900 [thread overview]
Message-ID: <20241008053100.GD10794@google.com> (raw)
In-Reply-To: <20241007094511.GA10794@google.com>
On (24/10/07 18:45), Sergey Senozhatsky wrote:
> + /*
> + * Tell the file system to write back all dirty data and shut down if
> + * it hasn't been notified earlier.
> + */
> + if (!test_bit(GD_DEAD, &disk->state))
> + blk_report_disk_dead(disk, false);
> + /* TODO: big fat comment */
> + blk_queue_flag_set(QUEUE_FLAG_DYING, disk->queue);
> + __blk_mark_disk_dead(disk);
> +
> /*
> * Prevent new openers by unlinked the bdev inode.
> */
> @@ -657,18 +667,10 @@ void del_gendisk(struct gendisk *disk)
> bdev_unhash(part);
> mutex_unlock(&disk->open_mutex);
>
> - /*
> - * Tell the file system to write back all dirty data and shut down if
> - * it hasn't been notified earlier.
> - */
> - if (!test_bit(GD_DEAD, &disk->state))
> - blk_report_disk_dead(disk, false);
> -
> /*
> * Drop all partitions now that the disk is marked dead.
> */
> mutex_lock(&disk->open_mutex);
> - __blk_mark_disk_dead(disk);
> xa_for_each_start(&disk->part_tbl, idx, part, 1)
> drop_partition(part);
> mutex_unlock(&disk->open_mutex);
> @@ -714,6 +716,10 @@ void del_gendisk(struct gendisk *disk)
> rq_qos_exit(q);
> blk_mq_unquiesce_queue(q);
>
> + /* TODO: big fat comment */
> + if (test_bit(GD_OWNS_QUEUE, &disk->state))
if (!test_bit()), muppet.
> + blk_queue_flag_clear(QUEUE_FLAG_DYING, disk->queue);
next prev parent reply other threads:[~2024-10-08 5:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 8:56 block: del_gendisk() vs blk_queue_enter() race condition Sergey Senozhatsky
2024-10-03 13:36 ` Christoph Hellwig
2024-10-03 13:43 ` Christoph Hellwig
2024-10-03 14:00 ` Sergey Senozhatsky
2024-10-03 14:17 ` Sergey Senozhatsky
2024-10-04 4:21 ` Sergey Senozhatsky
2024-10-04 6:45 ` Christoph Hellwig
2024-10-04 7:48 ` Sergey Senozhatsky
2024-10-04 7:49 ` Sergey Senozhatsky
2024-10-04 12:20 ` Christoph Hellwig
2024-10-04 14:32 ` Sergey Senozhatsky
2024-10-07 6:10 ` Christoph Hellwig
2024-10-07 9:45 ` Sergey Senozhatsky
2024-10-08 5:31 ` Sergey Senozhatsky [this message]
2024-10-04 14:41 ` Sergey Senozhatsky
2024-10-03 13:55 ` Sergey Senozhatsky
2024-10-08 4:02 ` YangYang
2024-10-08 5:19 ` Sergey Senozhatsky
2024-10-08 5:26 ` Sergey Senozhatsky
2024-10-08 5:56 ` Christoph Hellwig
2024-10-08 6:04 ` Christoph Hellwig
2024-10-08 6:10 ` Sergey Senozhatsky
2024-10-08 8:13 ` Christoph Hellwig
2024-10-08 8:20 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241008053100.GD10794@google.com \
--to=senozhatsky@chromium.org \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=yang.yang@vivo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.