From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs/048: amend property validation cases
Date: Wed, 3 Apr 2019 08:32:22 +0800 [thread overview]
Message-ID: <62f07675-128d-d68d-90e6-65044ec78e8a@oracle.com> (raw)
In-Reply-To: <903ccfcc-dfaf-3543-c29c-9d0c91125b75@gmail.com>
On 2/4/19 8:51 PM, Nikolay Borisov wrote:
>
>
> On 2.04.19 г. 13:07 ч., Anand Jain wrote:
>> Add more property validation cases which are fixed by the patches [1]
>> [1]
>> btrfs: fix property validate fail should not increment generation
>> btrfs: open code btrfs_set_prop in inherit_prop
>> btrfs: fix vanished compression property after failed set
>> btrfs: fix zstd compression parameter
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> (As this fstest patch depends on the kernel patches,
>> this patch isn't sent to fstests mailing list yet).
>>
>
> Doesn't matter, it's fine to have a test merged before respective kernel
> patches have landed.
Ok.
> In fact there is one btrfs test (can't remember
> which one) authored by you which is failing, yet the respective kernel
> patches have never been sent to the mailing list.
fstests is also a good place to record known issues. Otherwise we can
create a group of known-issues with in fstests. What do you think?
Currently we have these two fstests failing because its fix is not
yet in the kernel.
btrfs/172:
Exposed bug: Punch hole fails at ENOSPC only for the misaligned offset.
Because punch hole has to zero a partial block in case of misaligned
offset. Do you know how to fix? Of late I started believing its a
limitation rather than bug. If we agree we can decompose and reuse
btrfs/172 for something else.
btrfs/154:
Exposed bug: Reappeared missing device fakes its assembly to the
volume.
Fix (as indicated in btrfs/154) V5 is in the mailing list, with
accepted review comments.
next prev parent reply other threads:[~2019-04-03 0:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 10:07 [PATCH 0/4 RESEND] btrfs: fix property bugs Anand Jain
2019-04-02 10:07 ` [PATCH 1/4 RESEND] btrfs: fix zstd compression parameter Anand Jain
2019-04-02 22:09 ` David Sterba
2019-04-02 10:07 ` [PATCH] fstests: btrfs/048: amend property validation cases Anand Jain
2019-04-02 12:51 ` Nikolay Borisov
2019-04-03 0:32 ` Anand Jain [this message]
2019-04-02 10:07 ` [PATCH 2/4 RESEND] btrfs: fix vanished compression property after failed set Anand Jain
2019-04-02 13:00 ` Nikolay Borisov
2019-04-02 22:14 ` David Sterba
2019-04-02 10:07 ` [PATCH 3/4 RESEND] btrfs: open code btrfs_set_prop in inherit_prop Anand Jain
2019-04-02 13:35 ` Nikolay Borisov
2019-04-02 21:41 ` David Sterba
2019-04-02 23:24 ` David Sterba
2019-04-03 0:42 ` Anand Jain
2019-04-02 21:41 ` David Sterba
2019-04-02 10:07 ` [PATCH 4/4 RESEND] btrfs: fix property validate fail should not increment generation Anand Jain
2019-04-02 13:45 ` Nikolay Borisov
2019-04-02 21:13 ` David Sterba
2019-04-02 22:04 ` David Sterba
2019-04-02 23:03 ` Anand Jain
2019-04-03 16:54 [PATCH] fstests: btrfs/048: amend property validation cases Anand Jain
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=62f07675-128d-d68d-90e6-65044ec78e8a@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=n.borisov.lkml@gmail.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 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.