From: Ronnie Sahlberg <lsahlber@redhat.com>
To: linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>,
Pavel Shilovsky <pshilov@microsoft.com>
Subject: [PATCH 0/2] Start to fix fallocate support
Date: Wed, 13 Mar 2019 14:37:47 +1000 [thread overview]
Message-ID: <20190313043749.832-1-lsahlber@redhat.com> (raw)
Steve, Pavel
These initial two patches fixes fallocate -z (zero range) support against
windows2016 shares. This is a different case than what causes generic/469
to fail against samba shares but the approach for all these failures should
be similar.
It is a WIP in that it only addresses one single instance of this general
limited fallocate support in cifs.ko.
Next steps if you agree this is the way to go, would be to try to think
about how we can expand this to some/all of the othter cases as well
but perhaps without making too much code duplication.
Steve, can you run this against the buildbot and see that there are no new
failures from it?
next reply other threads:[~2019-03-13 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 4:37 Ronnie Sahlberg [this message]
2019-03-13 4:37 ` [PATCH 1/2] cifs: add SMB2_ioctl_init/free helpers to be used with compounding Ronnie Sahlberg
2019-03-13 4:37 ` [PATCH 2/2] cifs: fix smb3_zero_range so it can expand the file-size when required Ronnie Sahlberg
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=20190313043749.832-1-lsahlber@redhat.com \
--to=lsahlber@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pshilov@microsoft.com \
--cc=smfrench@gmail.com \
/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).