linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ike Panhc <ike.pan@canonical.com>
To: dann frazier <dann.frazier@canonical.com>,
	"Theodore Y. Ts'o" <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	yanaijie@huawei.com, colin.king@canonical.com,
	kamal.mostafa@canonical.com
Subject: Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap
Date: Wed, 11 Jul 2018 16:57:16 +0800	[thread overview]
Message-ID: <b39169ad-2237-0a4f-e3d1-afc51ac10fa5@canonical.com> (raw)
In-Reply-To: <20180710204329.GB20459@xps13.dannf>

On 07/11/2018 04:43 AM, dann frazier wrote:
> On Tue, Jul 10, 2018 at 10:51:43AM -0600, dann frazier wrote:
>> On Sat, Jul 07, 2018 at 12:10:18AM -0400, Theodore Y. Ts'o wrote:
>>> On Fri, Jul 06, 2018 at 11:43:24AM -0600, dann frazier wrote:
>>>> Hi,
>>>>   We're seeing a regression triggered by the stress-ng[*] "chdir" test
>>>> that I've bisected to:
>>>>
>>>> 044e6e3d74a3 ext4: don't update checksum of new initialized bitmaps
>>>>
>>>> So far we've only seen failures on servers based on HiSilicon's family
>>>> of ARM64 SoCs (D05/Hi1616 SoC, D06/Hi1620 SoC). On these systems it is
>>>> very reproducible.
>>>
>>> Thanks for the report.  Can you verify whether or not this patch fixes
>>> things for you?
>>
>> hey Ted,
>>   Sorry for the delayed response - was afk for a long weekend.
>> Your patch does seem to fix the issue for me - after applying the
>> patch, I was able to survive 20 iterations (and counting), where
>> previously it would always fail the first time.
>>
>> However, I've received a conflicting report from a colleague who
>> appears to still be seeing errors. I'll get back to you ASAP once I am
>> able to (in-?)validate that observation.
> 
> OK - I believe I found an explanation for my colleague's continued
> test failures after applying the patch. The filesystem being used may
> have already been corrupted from a previous run, and the test w/ your
> patch just tripped over it. Details are here starting in comment #9 if
> you'd like to look them over:
> 
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780137
> 
>   -dann
> 

Review console log and on each run I have filesystem rebuild. The problem
is that mke2fs I am using is 1.44.3-rc2. I am now reseting the environment
and re-test.

-- Ike

  reply	other threads:[~2018-07-11  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 17:43 [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap dann frazier
2018-07-07  4:10 ` Theodore Y. Ts'o
2018-07-10 16:51   ` dann frazier
2018-07-10 20:43     ` dann frazier
2018-07-11  8:57       ` Ike Panhc [this message]
2018-07-12 23:08         ` Theodore Y. Ts'o
2018-07-14 11:21           ` dann frazier
2018-07-16 23:13             ` dann frazier

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=b39169ad-2237-0a4f-e3d1-afc51ac10fa5@canonical.com \
    --to=ike.pan@canonical.com \
    --cc=colin.king@canonical.com \
    --cc=dann.frazier@canonical.com \
    --cc=kamal.mostafa@canonical.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yanaijie@huawei.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).