From: Ronnie Sahlberg <lsahlber@redhat.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/1] cifs: setfattr -x test for cifs
Date: Mon, 11 Feb 2019 15:19:31 +1000 [thread overview]
Message-ID: <20190211051932.20542-1-lsahlber@redhat.com> (raw)
List,
Please find a small test for cifs that tests that setfattr -x for a non existing attribute will fail correctly.
This is for a bug we recently fixed in cifs.ko where we used to return successr, since that is what the SMB2 response
from the server would be.
Xfstests already have testing for setfattr -x for nonexisting attributes in generic/097 but we can not use that test in cifs since we
can only allow the use of the user namespace. (No way to lock down access to read/write EA subspaces such as 'system.' prefixes and such.)
Since tests only tests a small subset of generic/097 it made more sense to me to add this as a cifs specific
test instead of adding a new, redundant, generic/* test.
next reply other threads:[~2019-02-11 5:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 5:19 Ronnie Sahlberg [this message]
2019-02-11 5:19 ` [PATCH] cifs: add test that setfattr -x fails non-existing EAs Ronnie Sahlberg
2019-02-11 21:51 ` Dave Chinner
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=20190211051932.20542-1-lsahlber@redhat.com \
--to=lsahlber@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).