[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjiU5Fq7aG0-H6QN1ZsK-U3Hw1K310N2z_eCPPDTKeysA@mail.gmail.com>
Date: Wed, 2 Dec 2020 12:42:08 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ira Weiny <ira.weiny@...el.com>
Cc: Eric Sandeen <sandeen@...hat.com>,
Miklos Szeredi <mszeredi@...hat.com>,
David Howells <dhowells@...hat.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-man <linux-man@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
xfs <linux-xfs@...r.kernel.org>,
Ext4 Developers List <linux-ext4@...r.kernel.org>,
Xiaoli Feng <xifeng@...hat.com>
Subject: Re: [PATCH 1/2] uapi: fix statx attribute value overlap for DAX & MOUNT_ROOT
On Tue, Dec 1, 2020 at 6:16 PM Ira Weiny <ira.weiny@...el.com> wrote:
>
> This will force a change to xfstests at a minimum. And I do know of users who
> have been using this value. But I have gotten inquires about using the feature
> so there are users out there.
If it's only a few tests that fail, I wouldn't worry about it, and the
tests should just be updated.
But if there are real user concerns, we may need to have some kind of
compat code. Because of the whole "no regressions" thing.
What would the typical failure cases be in practice?
Linus
Powered by blists - more mailing lists