From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 54474C48BE2 for ; Thu, 20 Jun 2019 05:28:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1F752214AF for ; Thu, 20 Jun 2019 05:28:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="vej6/UOM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726082AbfFTF2u (ORCPT ); Thu, 20 Jun 2019 01:28:50 -0400 Received: from mail-yw1-f65.google.com ([209.85.161.65]:42118 "EHLO mail-yw1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725912AbfFTF2u (ORCPT ); Thu, 20 Jun 2019 01:28:50 -0400 Received: by mail-yw1-f65.google.com with SMTP id s5so635431ywd.9; Wed, 19 Jun 2019 22:28:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=975n1pRlZvHWVrvlkCM9JYyTq8SwMn3AiFj33aMVVOw=; b=vej6/UOM56QFAi4RyCek7x+FHM10VJXhjV/yBMJfwJ/eLHPl/9xBs6cjl3YT0ZR13b aLvZKSyg9FIFJ9XFUBMDs5FqqLuaCi6s+POOE+WWpxjo1V617a5seaK8iL+wKpEdb/tK wakna1lltAvzWri0DuT0nSEomO1/NOc41gFdYhQPTgCuajhMt7t9Umcnh/SP3aSG1VOy o1wbGss0XoZpSb5ygcqJSa7lkutA0d14zDv7LLlbSZVd2YTjiGUt2R8oIWy5BPCmaDew bmxSGV8z5XsBfXo55pM6kktBgRr19wB8GVY+XFwtsIVjd8MgNdzDpFZd5yKIFo+vdViy 55HA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=975n1pRlZvHWVrvlkCM9JYyTq8SwMn3AiFj33aMVVOw=; b=Ut16fV0yBrxZUc+s2+FwkREG4JUc6teC7gAUlH78XRtzEqwWx7IiYZI+2tkdcSYb75 LPgGkCqtd8lcgPZN8/dVmKVvk/JOIPBKZjYr5EQkoEOquNBZALJyhnYvMFgWXRJ4CPRq EVGzEs/tj7SgsURoPaIdYst6UHruXpHiSVd4p2KuujbkZ6ZPvR49KHzEkRzClwT6iGWN L/pUtrDoOeYjpuYT3QkeUMn1QHwncu5+fZhZccLfczvX2XY/Z2LafruSEzfeFIkga7yZ rxNccG/zvCzN5eYb+svxFnIsw76wxubDKpPm/nmxZSvqT1k4iPE6Q9hof/KgBxvouO8U 7daQ== X-Gm-Message-State: APjAAAW69uyvTqQJFVftjtF7vDAThF77eC3ozKVswlag8zsThr2TWK0t oa09pneZEm3RG8CMWFPlM1bpNU/Dnn7I9tlrdJk= X-Google-Smtp-Source: APXvYqyc/TU+xc17P9uKRN/o3l801PdGZD7XU2NmiikDAEG+lkR5IHdIyZnss8a9qeKHKIpBeaJc2SwfWgFhaSSjr4o= X-Received: by 2002:a81:50d5:: with SMTP id e204mr18579529ywb.379.1561008529213; Wed, 19 Jun 2019 22:28:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Amir Goldstein Date: Thu, 20 Jun 2019 08:28:37 +0300 Message-ID: Subject: Re: [SMB3][PATCH] fix copy_file_range when copying beyond end of source file To: Steve French Cc: CIFS , samba-technical , linux-fsdevel , "Darrick J. Wong" Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Thu, Jun 20, 2019 at 4:44 AM Steve French wrote: > > Patch attached fixes the case where copy_file_range over an SMB3 mount > tries to go beyond the end of file of the source file. This fixes > xfstests generic/430 and generic/431 > > Amir's patches had added a similar change in the VFS layer... BTW, Steve, do you intend to pull Darrick's copy-file-range-fixes branch for 5.3 and add the extra cifs "file_modified" patch? Thanks, Amir.