Return-Path: Received: from mx2.suse.de ([195.135.220.15]:48053 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756420AbbHZNBe (ORCPT ); Wed, 26 Aug 2015 09:01:34 -0400 Date: Wed, 26 Aug 2015 15:00:57 +0200 From: David Sterba To: Peng Tao Cc: Linux NFS Mailing List , Trond Myklebust , Anna Schumaker , Christoph Hellwig , Zach Brown , Darren Hart , Bruce Fields , Jeff Layton , linux-btrfs@vger.kernel.org, Devel FS Linux Subject: Re: [PATCH RFC 02/11] vfs/btrfs: add .clone_range file operation Message-ID: <20150826130057.GW10756@suse.cz> Reply-To: dsterba@suse.cz References: <1440516829-116041-1-git-send-email-tao.peng@primarydata.com> <1440516829-116041-3-git-send-email-tao.peng@primarydata.com> <20150826080111.GV10756@twin.jikos.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: On Wed, Aug 26, 2015 at 04:31:09PM +0800, Peng Tao wrote: > >> -#define BTRFS_IOC_CLONE _IOW(BTRFS_IOCTL_MAGIC, 9, int) > > > > The ioctl definition reuses the BTRFS_IOCTL_MAGIC (0x94), which is IMHO > > wrong. > > > I thought it breaks ABI if we choose a different value for the type > field of the ioctl. Am I misunderstanding it? The ioctl is now private to btrfs, you're going to define the new ABI so it IMHO should use the generic filesystem ioctl magic/namespace.