[0/2] Start to fix fallocate support

Message ID	20190313043749.832-1-lsahlber@redhat.com (mailing list archive)
Headers	show Return-Path: <linux-cifs-owner@kernel.org> 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 Message-Id: <20190313043749.832-1-lsahlber@redhat.com> Sender: linux-cifs-owner@vger.kernel.org Precedence: bulk
Series	Start to fix fallocate support \| expand [0/2] Start to fix fallocate support [1/2] cifs: add SMB2_ioctl_init/free helpers to be used with compounding [2/2] cifs: fix smb3_zero_range so it can expand the file-size when required

Message ID

20190313043749.832-1-lsahlber@redhat.com (mailing list archive)

Headers

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
Message-Id: <20190313043749.832-1-lsahlber@redhat.com>
Sender: linux-cifs-owner@vger.kernel.org
Precedence: bulk

Series

Start to fix fallocate support | expand

Message

Ronnie Sahlberg March 13, 2019, 4:37 a.m. UTC

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?