From: Theodore Ts'o <tytso@mit.edu>
To: Ramin Farajpour Cami <ramin.blackhat@gmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: CRASH : RCU detected stall
Date: Wed, 14 Jun 2017 08:55:24 -0400 [thread overview]
Message-ID: <20170614125524.qxg3dkfbcaqxscp3@thunk.org> (raw)
In-Reply-To: <CAKEzZ8yb_n+iCy8+_fYujc1LAbijjjd97+dEh9qrwNfx0GAqUw@mail.gmail.com>
On Wed, Jun 14, 2017 at 10:02:00AM +0430, Ramin Farajpour Cami wrote:
>
> Unfortunately it's not reproducible. do you have idea about it?
Nope. Note that this isn't necessarily an ext4 bug. We have two
complaints about an rcu_sched thread getting staved and an NMI handler
getting taking too long to run:
rcu_sched kthread starved for 22270 jiffies! g2951 c2950 f0x0
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 2.762 msecs
We also happened be doing writeback on another CPU and the ext4 thread
was doing a slab allocation.
What ultimiately caused the RCU starvation is not at all clear. Were
we spinning inside the slab allocator, or not? Getting some
magic-sysrq triggers to see if the PC was always in the slab allocator
would be useful. And if that's the case, it's not clear what might
have caused us to spinning in the slab allocator. It could be due to
some slab state getting corrupted by a previous system call, and ext4
was just unlucky enough to do the slab allocation which caused it to
go for a loop.
We just don't have enough information to do any kind of useful
investigation.
- Ted
prev parent reply other threads:[~2017-06-14 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKEzZ8wRAFxXOcgxzu2KkntvNz8QvGocWpH_xDbRxRg=7LgbPA@mail.gmail.com>
2017-06-13 17:30 ` CRASH : RCU detected stall Theodore Ts'o
[not found] ` <CAKEzZ8yb_n+iCy8+_fYujc1LAbijjjd97+dEh9qrwNfx0GAqUw@mail.gmail.com>
2017-06-14 12:55 ` Theodore Ts'o [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=20170614125524.qxg3dkfbcaqxscp3@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ramin.blackhat@gmail.com \
--cc=syzkaller@googlegroups.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