From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mike Snitzer <snitzer@redhat.com>,
Alasdair Kergon <agk@redhat.com>, Hannes Reinecke <hare@suse.de>,
Jens Axboe <axboe@kernel.dk>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
Pavel Tide <Pavel.TIde@veeam.com>
Subject: Re: [PATCH v7 1/3] block: add blk_mq_is_queue_frozen()
Date: Mon, 15 Mar 2021 15:06:08 +0300 [thread overview]
Message-ID: <20210315120608.GA30489@veeam.com> (raw)
In-Reply-To: <20210314091441.GA3773360@infradead.org>
The 03/14/2021 12:14, Christoph Hellwig wrote:
> On Fri, Mar 12, 2021 at 02:06:41PM -0500, Mike Snitzer wrote:
> > This is returning a frozen state that is immediately stale. I don't
> > think any code calling this is providing the guarantees you think it
> > does due to the racey nature of this state once the mutex is dropped.
>
> The code only uses it for asserts in the form of WARN_ONs.
But perhaps it is possible to come up with a more elegant solution?
I'll think about it.
--
Sergei Shtepa
Veeam Software developer.
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>, Mike Snitzer <snitzer@redhat.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
Pavel Tide <Pavel.TIde@veeam.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: [dm-devel] [PATCH v7 1/3] block: add blk_mq_is_queue_frozen()
Date: Mon, 15 Mar 2021 15:06:08 +0300 [thread overview]
Message-ID: <20210315120608.GA30489@veeam.com> (raw)
In-Reply-To: <20210314091441.GA3773360@infradead.org>
The 03/14/2021 12:14, Christoph Hellwig wrote:
> On Fri, Mar 12, 2021 at 02:06:41PM -0500, Mike Snitzer wrote:
> > This is returning a frozen state that is immediately stale. I don't
> > think any code calling this is providing the guarantees you think it
> > does due to the racey nature of this state once the mutex is dropped.
>
> The code only uses it for asserts in the form of WARN_ONs.
But perhaps it is possible to come up with a more elegant solution?
I'll think about it.
--
Sergei Shtepa
Veeam Software developer.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-03-15 12:06 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:44 [PATCH v7 0/3] block device interposer Sergei Shtepa
2021-03-12 15:44 ` [dm-devel] " Sergei Shtepa
2021-03-12 15:44 ` [PATCH v7 1/3] block: add blk_mq_is_queue_frozen() Sergei Shtepa
2021-03-12 15:44 ` [dm-devel] " Sergei Shtepa
2021-03-12 19:06 ` Mike Snitzer
2021-03-12 19:06 ` [dm-devel] " Mike Snitzer
2021-03-14 9:14 ` Christoph Hellwig
2021-03-14 9:14 ` [dm-devel] " Christoph Hellwig
2021-03-15 12:06 ` Sergei Shtepa [this message]
2021-03-15 12:06 ` Sergei Shtepa
2021-03-12 15:44 ` [PATCH v7 2/3] block: add bdev_interposer Sergei Shtepa
2021-03-12 15:44 ` [dm-devel] " Sergei Shtepa
2021-03-14 9:28 ` Christoph Hellwig
2021-03-14 9:28 ` [dm-devel] " Christoph Hellwig
2021-03-15 13:06 ` Sergei Shtepa
2021-03-15 13:06 ` [dm-devel] " Sergei Shtepa
2021-03-16 8:09 ` Ming Lei
2021-03-16 8:09 ` [dm-devel] " Ming Lei
2021-03-16 16:35 ` Sergei Shtepa
2021-03-16 16:35 ` [dm-devel] " Sergei Shtepa
2021-03-17 3:03 ` Ming Lei
2021-03-17 3:03 ` [dm-devel] " Ming Lei
2021-03-17 12:22 ` Sergei Shtepa
2021-03-17 12:22 ` [dm-devel] " Sergei Shtepa
2021-03-17 15:04 ` Mike Snitzer
2021-03-17 15:04 ` [dm-devel] " Mike Snitzer
2021-03-17 18:14 ` Sergei Shtepa
2021-03-17 18:14 ` [dm-devel] " Sergei Shtepa
2021-03-17 19:13 ` Mike Snitzer
2021-03-17 19:13 ` [dm-devel] " Mike Snitzer
2021-03-18 14:56 ` Sergei Shtepa
2021-03-18 14:56 ` [dm-devel] " Sergei Shtepa
2021-03-17 14:58 ` Mike Snitzer
2021-03-17 14:58 ` [dm-devel] " Mike Snitzer
2021-03-12 15:44 ` [PATCH v7 3/3] dm: add DM_INTERPOSED_FLAG Sergei Shtepa
2021-03-12 15:44 ` [dm-devel] " Sergei Shtepa
2021-03-12 19:00 ` Mike Snitzer
2021-03-12 19:00 ` [dm-devel] " Mike Snitzer
2021-03-15 12:29 ` Sergei Shtepa
2021-03-15 12:29 ` [dm-devel] " Sergei Shtepa
2021-03-14 9:30 ` Christoph Hellwig
2021-03-14 9:30 ` [dm-devel] " Christoph Hellwig
2021-03-15 13:25 ` Sergei Shtepa
2021-03-15 13:25 ` [dm-devel] " Sergei Shtepa
2021-03-16 15:23 ` Christoph Hellwig
2021-03-16 15:23 ` [dm-devel] " Christoph Hellwig
2021-03-16 15:25 ` Christoph Hellwig
2021-03-16 15:25 ` [dm-devel] " Christoph Hellwig
2021-03-16 16:20 ` Sergei Shtepa
2021-03-16 16:20 ` [dm-devel] " Sergei Shtepa
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=20210315120608.GA30489@veeam.com \
--to=sergei.shtepa@veeam.com \
--cc=Pavel.TIde@veeam.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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.