From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: Tests 112 and 469
Date: Tue, 30 Apr 2019 10:52:21 -0500 [thread overview]
Message-ID: <CAH2r5mtxU3aONRMaZLKEMPBWydDZgjSiBS07sHXXK0zUeBmUdQ@mail.gmail.com> (raw)
This patch is odd because it fails xfstests 112 and 469 to Azure, even
though Azure doesn't support the operation so should skip the same
part of the test with or without Ronnie's patch and tests should work.
commit d008b979e8e6196ab3f916ca076448f5c9f527f3 (HEAD, origin/for-next)
Author: Ronnie Sahlberg <lsahlber@redhat.com>
Date: Fri Apr 12 09:56:23 2019 +1000
cifs: zero-range does not require the file is sparse
Remove the conditional to fail zero-range if the file is not
flagged as sparse.
You can still zero out a range in SMB2 even for non-sparse files.
Tested with stock windows16 server.
Fixes 5 xfstests (033, 149, 155, 180, 349)
Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
--
Thanks,
Steve
reply other threads:[~2019-04-30 15:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAH2r5mtxU3aONRMaZLKEMPBWydDZgjSiBS07sHXXK0zUeBmUdQ@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs@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).