From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Eryu Guan <eguan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [4.11-rc6 bug] fstests cifs/001 failure with cifs 2.0/2.1/3.0 mounts
Date: Wed, 26 Apr 2017 17:52:50 +0100 [thread overview]
Message-ID: <1493225570.4270.25.camel@redhat.com> (raw)
In-Reply-To: <20170410043431.GB22845-+7p9VZFSOIEFmhoHi+V13ACJwEvxM/w9@public.gmane.org>
Hello Eryu,
I have identified a change in behaviour which leads to this error. I
have posted a patch which fixes this issue.
Sachin Prabhu
On Mon, 2017-04-10 at 12:34 +0800, Eryu Guan wrote:
> Hi all,
>
> Starting from 4.11-rc6 kernel, I noticed new cifs/001 failure, I
> tested
> with a local mount linux samba server, with v2.0/2.1/3.0 cifs mounts,
> and it's always reproducible.
>
> @@ -19,3 +19,13 @@
> XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> wrote 10240/10240 bytes at offset 0
> XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
> +clone failed: No such file or directory
>
> git bisect pointed the "first bad" commit to
>
> commit 620d8745b35daaf507186c26b40c7ea02aed131e
> Author: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Date: Fri Feb 10 16:03:51 2017 +0530
>
> Introduce cifs_copy_file_range()
>
> The earlier changes to copy range for cifs unintentionally
> disabled the more
> common form of server side copy.
>
> The patch introduces the file_operations helper
> cifs_copy_file_range()
> which is used by the syscall copy_file_range. The new file
> operations
> helper allows us to perform server side copies for SMB2.0 and 2.1
> servers as well as SMB 3.0+ servers which do not support the
> ioctl
> FSCTL_DUPLICATE_EXTENTS_TO_FILE.
>
> The new helper uses the ioctl FSCTL_SRV_COPYCHUNK_WRITE to
> perform
> server side copies. The helper is called by vfs_copy_file_range()
> only
> once an attempt to clone the file using the ioctl
> FSCTL_DUPLICATE_EXTENTS_TO_FILE has failed.
>
> Signed-off-by: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Reviewed-by: Pavel Shilovsky <pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>
> CC: Stable <stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
> Signed-off-by: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>
> Not sure if test needs to be updated, if you need more info please
> let
> me know.
>
> Thanks,
> Eryu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs"
> in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-04-26 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 4:34 [4.11-rc6 bug] fstests cifs/001 failure with cifs 2.0/2.1/3.0 mounts Eryu Guan
[not found] ` <20170410043431.GB22845-+7p9VZFSOIEFmhoHi+V13ACJwEvxM/w9@public.gmane.org>
2017-04-26 16:52 ` Sachin Prabhu [this message]
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=1493225570.4270.25.camel@redhat.com \
--to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=eguan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.