linux-kernel - Re: [PATCH 3/1] xfstests: generic/062: Do not run on newer kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <95fd9166-c809-5a2e-fb40-aba253c9faa6@schaufler-ca.com>
Date:   Fri, 3 Sep 2021 09:01:30 -0700
From:   Casey Schaufler <casey@...aufler-ca.com>
To:     Bruce Fields <bfields@...hat.com>, Vivek Goyal <vgoyal@...hat.com>
Cc:     Andreas Gruenbacher <agruenba@...hat.com>,
        fstests <fstests@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>, virtio-fs@...hat.com,
        Daniel Walsh <dwalsh@...hat.com>,
        David Gilbert <dgilbert@...hat.com>,
        Christian Brauner <christian.brauner@...ntu.com>,
        Casey Schaufler <casey.schaufler@...el.com>,
        LSM <linux-security-module@...r.kernel.org>,
        selinux@...r.kernel.org, Theodore Ts'o <tytso@....edu>,
        Miklos Szeredi <miklos@...redi.hu>,
        Giuseppe Scrivano <gscrivan@...hat.com>,
        stephen.smalley.work@...il.com, Dave Chinner <david@...morbit.com>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [PATCH 3/1] xfstests: generic/062: Do not run on newer kernels

On 9/3/2021 8:50 AM, Bruce Fields wrote:
> On Fri, Sep 3, 2021 at 11:43 AM Vivek Goyal <vgoyal@...hat.com> wrote:
>> On Fri, Sep 03, 2021 at 10:42:34AM -0400, Bruce Fields wrote:
>>> Well, we could also look at supporting trusted.* xattrs over NFS.  I
>>> don't know much about them, but it looks like it wouldn't be a lot of
>>> work to specify, especially now that we've already got user xattrs?
>>> We'd just write a new internet draft that refers to the existing
>>> user.* xattr draft for most of the details.
>> Will be nice if we can support trusted.* xattrs on NFS.
> Maybe I should start a separate thread for that.  Who would need to be
> on it to be sure we get this right?

I would like to be included. It would probably be a good idea to
include the LSM list, linux-security-module@...r.kernel.org. I'll leave
the networking and filesystem folks to speak for themselves.

>
> --b.
>