FS/XFS testing framework
 help / color / mirror / Atom feed
From: Sun Ke <sunke32@huawei.com>
To: <fstests@vger.kernel.org>, <zlang@redhat.com>
Cc: <yangerkun@huawei.com>, <tytso@mit.edu>
Subject: Re: [xfstests PATCH v3] ext4: Add a test for rename with RENAME_WHITEOUT
Date: Thu, 4 Feb 2021 15:59:52 +0800	[thread overview]
Message-ID: <53ef6abe-d01c-8ecd-d20d-1b2fc172676e@huawei.com> (raw)
In-Reply-To: <20210202160527.GB14354@localhost.localdomain>

Hi, Zorro

在 2021/2/3 0:05, Zorro Lang 写道:
> On Tue, Feb 02, 2021 at 08:39:56PM +0800, Sun Ke wrote:
>> Fill the disk space, try to create some files and rename a file, mount
>> again, list directory contents and triggers some errors. It is a
>> regression test for kernel commit 6b4b8e6b4ad8 ("ext4: ext4: fix bug for
>> rename with RENAME_WHITEOUT")
>>
>> Signed-off-by: Sun Ke <sunke32@huawei.com>
>> ---
>> v3: use _check_dmesg_for() and modify the group.
>> ---
> I helped to re-write this case(without loopdev, dmesg check and ext4 specific
> things) as below[1]. It can reproduce that bug[2], and test passed on fixed
> kernel[3].
Thanks for your help. Yes, it can reproduce the bug on ext4 test.
>
> But I found another problem, we can't 100% make sure that renameat2 hit ENOSPC,
> even if we can't create any empty file. That renameat2 line still succeed on
> my XFS test. And Eric Sandeen even can't trigger that rename ENOSPC on his
> machine.

The same as  Eric,  I can not trigger that rename ENOSPC on my machine 
on xfs test.

Thanks,

Sun Ke


> .

  parent reply	other threads:[~2021-02-04  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 12:39 [xfstests PATCH v3] ext4: Add a test for rename with RENAME_WHITEOUT Sun Ke
2021-02-02 16:05 ` Zorro Lang
2021-02-03  6:20   ` Zorro Lang
2021-02-04  7:59   ` Sun Ke [this message]
2021-02-04 13:11     ` Zorro Lang

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=53ef6abe-d01c-8ecd-d20d-1b2fc172676e@huawei.com \
    --to=sunke32@huawei.com \
    --cc=fstests@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yangerkun@huawei.com \
    --cc=zlang@redhat.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