From: Nikolay Borisov <kernel@kyup.com>
To: John Stoffel <john@stoffel.org>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>, Marian Marinov <mm@1h.com>,
Jan Kara <jack@suse.com>
Subject: Re: Hard lockup in ext4_finish_bio
Date: Thu, 8 Oct 2015 17:37:07 +0300 [thread overview]
Message-ID: <56167F93.8010408@kyup.com> (raw)
In-Reply-To: <22038.32498.570540.37956@quad.stoffel.home>
On 10/08/2015 05:34 PM, John Stoffel wrote:
> Great bug report, but you're missing the info on which kernel you're
This is on 3.12.47 (self compiled). It was evident on my initial post,
but I did forget to mention that in the reply. Also, I suspect even
current kernel are susceptible to this since the locking in question
hasn't changed.
Regards,
Nikolay
next prev parent reply other threads:[~2015-10-08 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 11:46 Hard lockup in ext4_finish_bio Nikolay Borisov
2015-10-08 14:15 ` Nikolay Borisov
2015-10-08 14:34 ` John Stoffel
2015-10-08 14:37 ` Nikolay Borisov [this message]
2015-10-08 18:56 ` John Stoffel
2015-10-09 8:05 ` Nikolay Borisov
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=56167F93.8010408@kyup.com \
--to=kernel@kyup.com \
--cc=jack@suse.com \
--cc=john@stoffel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm@1h.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.