From: Vivek Goyal <vgoyal@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [xattr] 6e21a50861: ltp.setxattr02.fail
Date: Tue, 7 Sep 2021 13:52:22 -0400 [thread overview]
Message-ID: <YTem1rCPHsgoohkp@redhat.com> (raw)
In-Reply-To: <YTXNXOKbrl17Lx+s@yuki>
On Mon, Sep 06, 2021 at 10:12:12AM +0200, Cyril Hrubis wrote:
> Hi!
> > commit: 6e21a5086100cebefd21a3058a9e1160668f84fa ("xattr: Allow user.* xattr on symlink and special files")
> > https://github.com/rhvgoyal/linux user-xattr-symlink-v3
>
> The test that fails is a test that asserts that you can't add extended
> attributes to a block or char device and it's obvious why this fails.
>
> Feel free to ignore this failure, we will have to fix the tests once/if
> this patchset gets accepted upstream.
Yes, if patches get accepted, test will have to be fixed. I fixed
xfstest too in the same patch series.
But at the moment it looks like there is resistance to the idea of
allowing user.* xattrs on symlinks and special files.
Vivek
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: lkp@lists.01.org, kernel test robot <oliver.sang@intel.com>,
lkp@intel.com, ltp@lists.linux.it
Subject: Re: [LTP] [xattr] 6e21a50861: ltp.setxattr02.fail
Date: Tue, 7 Sep 2021 13:52:22 -0400 [thread overview]
Message-ID: <YTem1rCPHsgoohkp@redhat.com> (raw)
Message-ID: <20210907175222.W2AfTx_I0J_T4d1A_PwGRdu0P-pAzB2kySsLqiqo7-w@z> (raw)
In-Reply-To: <YTXNXOKbrl17Lx+s@yuki>
On Mon, Sep 06, 2021 at 10:12:12AM +0200, Cyril Hrubis wrote:
> Hi!
> > commit: 6e21a5086100cebefd21a3058a9e1160668f84fa ("xattr: Allow user.* xattr on symlink and special files")
> > https://github.com/rhvgoyal/linux user-xattr-symlink-v3
>
> The test that fails is a test that asserts that you can't add extended
> attributes to a block or char device and it's obvious why this fails.
>
> Feel free to ignore this failure, we will have to fix the tests once/if
> this patchset gets accepted upstream.
Yes, if patches get accepted, test will have to be fixed. I fixed
xfstest too in the same patch series.
But at the moment it looks like there is resistance to the idea of
allowing user.* xattrs on symlinks and special files.
Vivek
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: lkp@lists.01.org
Subject: Re: [LTP] [xattr] 6e21a50861: ltp.setxattr02.fail
Date: Tue, 07 Sep 2021 13:52:22 -0400 [thread overview]
Message-ID: <YTem1rCPHsgoohkp@redhat.com> (raw)
In-Reply-To: <YTXNXOKbrl17Lx+s@yuki>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
On Mon, Sep 06, 2021 at 10:12:12AM +0200, Cyril Hrubis wrote:
> Hi!
> > commit: 6e21a5086100cebefd21a3058a9e1160668f84fa ("xattr: Allow user.* xattr on symlink and special files")
> > https://github.com/rhvgoyal/linux user-xattr-symlink-v3
>
> The test that fails is a test that asserts that you can't add extended
> attributes to a block or char device and it's obvious why this fails.
>
> Feel free to ignore this failure, we will have to fix the tests once/if
> this patchset gets accepted upstream.
Yes, if patches get accepted, test will have to be fixed. I fixed
xfstest too in the same patch series.
But at the moment it looks like there is resistance to the idea of
allowing user.* xattrs on symlinks and special files.
Vivek
>
> --
> Cyril Hrubis
> chrubis(a)suse.cz
>
next prev parent reply other threads:[~2021-09-07 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 13:45 [LTP] [xattr] 6e21a50861: ltp.setxattr02.fail kernel test robot
2021-09-05 13:45 ` kernel test robot
2021-09-06 8:12 ` [LTP] " Cyril Hrubis
2021-09-06 8:12 ` Cyril Hrubis
2021-09-06 8:12 ` Cyril Hrubis
2021-09-07 17:52 ` Vivek Goyal [this message]
2021-09-07 17:52 ` Vivek Goyal
2021-09-07 17:52 ` Vivek Goyal
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=YTem1rCPHsgoohkp@redhat.com \
--to=vgoyal@redhat.com \
--cc=ltp@lists.linux.it \
/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.