[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190327023354.GB7389@localhost.localdomain>
Date: Tue, 26 Mar 2019 20:33:54 -0600
From: Keith Busch <kbusch@...nel.org>
To: "jianchao.wang" <jianchao.w.wang@...cle.com>
Cc: Jens Axboe <axboe@...nel.dk>,
"Busch, Keith" <keith.busch@...el.com>,
James Smart <jsmart2021@...il.com>,
Bart Van Assche <bvanassche@....org>,
Ming Lei <tom.leiming@...il.com>,
Josef Bacik <josef@...icpanda.com>,
linux-nvme <linux-nvme@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-block <linux-block@...r.kernel.org>,
Hannes Reinecke <hare@...e.de>,
Johannes Thumshirn <jthumshirn@...e.de>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>
Subject: Re: [PATCH V2 7/8] nvme: use blk_mq_queue_tag_inflight_iter
On Wed, Mar 27, 2019 at 10:27:57AM +0800, jianchao.wang wrote:
> As the comment above, the stable request maybe something that has been freed due to following case,
> 1. a hctx->fq.flush_rq of dead request_queue that shares the same tagset
> 2. a removed io scheduler's sched request
> and this freed request could be allocated by others which may change the field of request->state.
You're not explaing how that request->state is changed. I understand the
request can be reallocated, but what is changing its state?
Powered by blists - more mailing lists