From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] block: avoid to hold q->limits_lock across APIs for atomic update queue limits
Date: Thu, 19 Dec 2024 07:15:14 +0100 [thread overview]
Message-ID: <20241219061514.GA19575@lst.de> (raw)
In-Reply-To: <Z2Iu1CAAC-nE-5Av@fedora>
On Wed, Dec 18, 2024 at 10:09:24AM +0800, Ming Lei wrote:
> This way looks good, just commit af2814149883 ("block: freeze the queue in
> queue_attr_store") needs to be reverted, and freeze/unfreeze has to be
> added to each queue attribute .store() handler.
Actually the sysfs handlers need a lot more work, including sorting
out the sysfs_lock mess. Gimme a little time to work on it.
next prev parent reply other threads:[~2024-12-19 6:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 8:02 [PATCH 0/2] block: fix deadlock caused by atomic limits update Ming Lei
2024-12-16 8:02 ` [PATCH 1/2] block: avoid to hold q->limits_lock across APIs for atomic update queue limits Ming Lei
2024-12-16 15:49 ` Christoph Hellwig
2024-12-17 1:52 ` Ming Lei
2024-12-17 4:40 ` Christoph Hellwig
2024-12-17 7:05 ` Ming Lei
2024-12-17 7:19 ` Christoph Hellwig
2024-12-17 7:30 ` Ming Lei
2024-12-17 16:07 ` Damien Le Moal
2024-12-18 2:09 ` Ming Lei
2024-12-18 11:33 ` Nilay Shroff
2024-12-18 13:40 ` Ming Lei
2024-12-18 14:05 ` Nilay Shroff
2024-12-18 14:57 ` Damien Le Moal
2024-12-19 6:20 ` Christoph Hellwig
2024-12-19 7:16 ` Nilay Shroff
2024-12-21 13:03 ` Nilay Shroff
2024-12-30 9:02 ` Ming Lei
2024-12-30 23:29 ` Damien Le Moal
2025-01-01 11:17 ` Nilay Shroff
2024-12-19 6:17 ` Christoph Hellwig
2024-12-19 6:15 ` Christoph Hellwig [this message]
2024-12-16 8:02 ` [PATCH 2/2] block: remove queue_limits_cancel_update() Ming Lei
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=20241219061514.GA19575@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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.