From: Sasha Levin <sasha.levin@oracle.com>
To: Tejun Heo <tj@kernel.org>
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: Wed, 09 Sep 2015 14:32:33 -0400 [thread overview]
Message-ID: <55F07B41.3030306@oracle.com> (raw)
In-Reply-To: <20150904173650.GF25329@mtj.duckdns.org>
On 09/04/2015 01:36 PM, Tejun Heo wrote:
> Hello,
>
> On Fri, Sep 04, 2015 at 01:20:42PM -0400, Sasha Levin wrote:
>>> 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.
>>
>> [268773.335933] kasan: GPF could be caused by NULL-ptr deref or user memory accessgeneral protection fault: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC KASAN
>> [268773.337986] Modules linked in:
>> [268773.338470] CPU: 3 PID: 12812 Comm: trinity-c10 Not tainted 4.2.0-next-20150902-sasha-00045-gd0866f3-dirty #2528
>> [268773.339903] task: ffff8802f56e4000 ti: ffff880322e10000 task.ti: ffff880322e10000
>> [268773.340943] RIP: 0010:[<ffffffffaa8b8284>] [<ffffffffaa8b8284>] trace_event_raw_event_writeback_dirty_page+0x1b4/0x420
>
> Hmm.... did this happen while or around a device removal event? I'm
> trying to figure out whether an unregistered bdi can have inodes.
I ran some more tests, and I didn't see device removal events close to it.
Thanks,
Sasha
prev parent reply other threads:[~2015-09-09 18:32 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
2015-09-04 17:20 ` Sasha Levin
2015-09-04 17:36 ` Tejun Heo
2015-09-09 18:32 ` Sasha Levin [this message]
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=55F07B41.3030306@oracle.com \
--to=sasha.levin@oracle.com \
--cc=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
/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).