From: Tejun Heo <tj@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: rostedt@goodmis.org, mingo@redhat.com, axboe@fb.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] writeback: verify that underlying dev exists before getting its name
Date: Fri, 4 Sep 2015 12:47:29 -0400 [thread overview]
Message-ID: <20150904164729.GD25329@mtj.duckdns.org> (raw)
In-Reply-To: <1441385118-27199-1-git-send-email-sasha.levin@oracle.com>
On Fri, Sep 04, 2015 at 12:45:18PM -0400, Sasha Levin wrote:
> We can't assume there is always an underlying device and must verify that
> as well. Otherwise, we'd deref a NULL ptr here.
Do you have backtrace of this happening? There's a bug in cleanup
path which causes oops (patch is being tested) and this may just be a
symptom of the same problem.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-09-04 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 16:45 [PATCH] writeback: verify that underlying dev exists before getting its name Sasha Levin
2015-09-04 16:47 ` Tejun Heo [this message]
2015-09-04 17:20 ` Sasha Levin
2015-09-04 17:36 ` Tejun Heo
2015-09-09 18:32 ` Sasha Levin
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=20150904164729.GD25329@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).