From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH RFC 02/11] vfs/btrfs: add .clone_range file operation Date: Wed, 26 Aug 2015 06:07:12 -0700 Message-ID: <20150826130712.GA6958@infradead.org> 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> <20150826130057.GW10756@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: dsterba@suse.cz, Peng Tao , 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 Return-path: Content-Disposition: inline In-Reply-To: <20150826130057.GW10756@suse.cz> Sender: linux-btrfs-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Aug 26, 2015 at 03:00:57PM +0200, David Sterba wrote: > > 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. No, that's completly backwards. We move up ioctls that have prooven to be generally useful to common code, and we've done that with various extN and XFS ones already.