From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [BUG] softlockup observed with 64k block size on ppc64
Date: Tue, 25 Oct 2016 18:49:54 +0530 [thread overview]
Message-ID: <17387849.5EiRHCrpou@localhost.localdomain> (raw)
In-Reply-To: <20161025081319.GC16260@quack2.suse.cz>
On Tuesday, October 25, 2016 10:13:19 AM Jan Kara wrote:
> Hi!
>
> On Mon 24-10-16 14:10:02, Chandan Rajendra wrote:
> > The following soft lockup occurs when fstests' ext4/303 test is executed with
> > 64k block size on a ppc64 machine running linux-4.8 kernel.
>
> Thanks for report! I had a look into the code and I'm not sure why this
> happens. Is this reproducible? Did it happen also with older kernels?
Yes, This issue can be recreated every single time the test is executed. The
bug is present atleast from linux-v4.0 version. I haven't verified if the bug
is present in earlier versions of the kernel.
--
chandan
prev parent reply other threads:[~2016-10-25 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 8:40 [BUG] softlockup observed with 64k block size on ppc64 Chandan Rajendra
2016-10-25 8:13 ` Jan Kara
2016-10-25 13:19 ` Chandan Rajendra [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=17387849.5EiRHCrpou@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox