From: Mike Snitzer <snitzer@redhat.com>
To: "Li, Zhen-Hua" <zhen-hual@hp.com>
Cc: linux-kernel@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com, Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
Date: Wed, 28 May 2014 11:03:14 -0400 [thread overview]
Message-ID: <20140528150314.GB25249@redhat.com> (raw)
In-Reply-To: <1401258172-17381-1-git-send-email-zhen-hual@hp.com>
On Wed, May 28 2014 at 2:22am -0400,
Li, Zhen-Hua <zhen-hual@hp.com> wrote:
> This patch is trying to fix a kernel crash bug.
>
> When kernel boots on a HP large system, it crashes.
> The reason is when blk_rq_init is called, the second parameter rq , which
> is a member as q->flush_rq, is NULL. Kernel does not allocate space for it.
>
> This fix adds an alloc for flush_rq member when request_queue is created in
> struct mapped_device *alloc_dev(int minor);
>
> Bug Details:
> Error message:
>
> [ 62.931942] BUG: unable to handle kernel NULL pointer dereference at (null)
> [ 62.931949] IP: [<ffffffff812b3f30>] blk_rq_init+0x40/0x160^M
> [ 62.931949] PGD 0 ^M
> [ 62.931951] Oops: 0002 [#1] SMP
You didn't specify which kernel you're running. But this was fixed for
v3.15-rc6 via linux.git commit 7982e90c3a5 ("block: fix q->flush_rq NULL
pointer crash on dm-mpath flush"). And then there was the follow-on fix
from linux.git commit 708f04d2ab ("block: free q->flush_rq in
blk_init_allocated_queue error paths")
So all this is to say: Nack to your patch, we've already fixed the issue
differently.
next prev parent reply other threads:[~2014-05-28 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 6:22 [PATCH 1/1] driver/md/block: Alloc space for member flush_rq Li, Zhen-Hua
2014-05-28 15:03 ` Mike Snitzer [this message]
2014-05-29 1:58 ` Li, Zhen-Hua
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=20140528150314.GB25249@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=zhen-hual@hp.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