From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Mike Snitzer <snitzer@redhat.com>, Ming Lei <ming.lei@canonical.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [PATCH] block: fully initialize queue in blk_mq_init_allocated_queue
Date: Fri, 13 Mar 2015 18:30:50 +0900 [thread overview]
Message-ID: <1426239050-2528-1-git-send-email-sergey.senozhatsky@gmail.com> (raw)
Commit c9e8c91f8a279b87eb0d94b037504ea9fc1bef7c
Author: Mike Snitzer <snitzer@redhat.com>
Date: Tue Mar 10 15:54:41 2015 -0400
blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
for some reason has moved queue allocation 'q = blk_alloc_queue_node()'
after 'percpu_ref_init(&q->mq_usage_counter...)', so we are doing percpu
init on something that is not a request_queue.
Further commit 716452cd27b145d611e4399e7cc35df6c943686e
Author: Mike Snitzer <snitzer@redhat.com>
Date: Tue Mar 10 17:20:20 2015 -0400
blk-mq: add blk_mq_init_allocated_queue and export
has introduced abother issue.
In blk_mq_init_queue() we allocate new request_queue:
uninit_q = blk_alloc_queue_node(GFP_KERNEL, set->numa_node);
if (!uninit_q)
return ERR_PTR(-ENOMEM);
and pass `uninit_q' as a 'request_queue *q' parameter to
blk_mq_init_allocated_queue():
q = blk_mq_init_allocated_queue(set, uninit_q);
blk_mq_init_allocated_queue(), however, firstly use passed `uninit_q' to init
its percpu, but then it allocates a new request_queue and returns it back,
not being properly initialized:
blk_mq_init_allocated_queue(struct blk_mq_tag_set *set, struct request_queue *q)
[..]
if (percpu_ref_init(&q->mq_usage_counter, blk_mq_usage_counter_release,
PERCPU_REF_INIT_ATOMIC, GFP_KERNEL))
goto err_hctxs;
q = blk_alloc_queue_node(GFP_KERNEL, set->numa_node);
if (!q)
goto err_hctxs;
[..]
return q;
Which eventually leads to different problems, including a NULL pointer
dereference.
Remove blk_alloc_queue_node() from blk_mq_init_allocated_queue() and use
supplied request_queue.
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
---
block/blk-mq.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index b838dfc..59fa239 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -1955,10 +1955,6 @@ struct request_queue *blk_mq_init_allocated_queue(struct blk_mq_tag_set *set,
PERCPU_REF_INIT_ATOMIC, GFP_KERNEL))
goto err_hctxs;
- q = blk_alloc_queue_node(GFP_KERNEL, set->numa_node);
- if (!q)
- goto err_hctxs;
-
setup_timer(&q->timeout, blk_mq_rq_timer, (unsigned long) q);
blk_queue_rq_timeout(q, 30000);
--
2.3.2.223.g7a9409c
next reply other threads:[~2015-03-13 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 9:30 Sergey Senozhatsky [this message]
2015-03-13 12:24 ` Mike Snitzer
2015-03-13 12:37 ` Sergey Senozhatsky
2015-03-13 14:17 ` next-20150313's block is broken, but fix available [was: Re: block: fully initialize queue in blk_mq_init_allocated_queue] Mike Snitzer
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=1426239050-2528-1-git-send-email-sergey.senozhatsky@gmail.com \
--to=sergey.senozhatsky@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=sergey.senozhatsky.work@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®