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=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 6CB9DC4360C for ; Fri, 27 Sep 2019 08:25:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 49D8A21850 for ; Fri, 27 Sep 2019 08:25:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726473AbfI0IZO (ORCPT ); Fri, 27 Sep 2019 04:25:14 -0400 Received: from mx2.suse.de ([195.135.220.15]:58578 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726118AbfI0IZO (ORCPT ); Fri, 27 Sep 2019 04:25:14 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id D4486AECB; Fri, 27 Sep 2019 08:25:12 +0000 (UTC) Date: Fri, 27 Sep 2019 10:25:10 +0200 From: Petr Vorel To: Amir Goldstein Cc: "Darrick J. Wong" , Dave Chinner , Cyril Hrubis , linux-xfs , linux-fsdevel , LTP List , "Michael Kerrisk (man-pages)" Subject: Re: copy_file_range() errno changes introduced in v5.3-rc1 Message-ID: <20190927082510.GA12604@dell5510> Reply-To: Petr Vorel References: <20190926155608.GC23296@dell5510> <20190926160432.GC9916@magnolia> <20190926161906.GD23296@dell5510> <20190926175700.GA12619@x230> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-xfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org Hi Amir, > > LTP hasn't defined yet any policy about changing errnos, > > as it's probably best to check whether change was intentional > > (like your obvious fixes) or not. > IIUC, copy_file_range02 was written after v5.3 changes to verify that > copy_file_range > stays unbroken. > As such, I would suggest that you check if kernel supports cross-fs copy, like > copy_file_range01 does and if it doesn't, skip the test entirely. > If some one ever backports cross-fs copy to any distro stable kernel, then one > would better also backkport all of those API fixes, otherwise test will fail. Thanks for a tip, I'll send a patch today. > Thanks, > Amir. Kind regards, Petr