Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754652AbaKSB7O (ORCPT ); Tue, 18 Nov 2014 20:59:14 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:54821 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754523AbaKSB7M (ORCPT ); Tue, 18 Nov 2014 20:59:12 -0500 Date: Wed, 19 Nov 2014 01:59:08 +0000 From: Al Viro To: Miklos Szeredi Cc: Andy Whitcroft , Serge Hallyn , Neil Brown , linux-unionfs@vger.kernel.org, Kernel Mailing List , Linus Torvalds Subject: Re: How to cope with two incompatible overlayfs formats out in the wild Message-ID: <20141119015908.GV7996@ZenIV.linux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 18, 2014 at 03:28:03PM +0100, Miklos Szeredi wrote: > So from mainline we need two things: > > - when mounting distinguish between old and new format. > > - userspace can detect which formats are supported by the kernel. > > If we'd have a different filesystem type for the old and new formats, > then that would solve both (checking /proc/filesystems would indicate > which one is supported). > > Unfortunately that would mean having to change "overlayfs" type to > something else in 3.18. Question is, is there some sane name which > would fit? "overlayfs2" is perhaps the best, but I'm not overly > enthusiastic about it. > > Any other ideas? Umm... What does the old one do when it sees workdir= in the options? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/