From: Christoph Hellwig Subject: Re: [RFC PATCH 0/7] dax, ext4: Synchronous page faults Date: Sun, 13 Aug 2017 02:25:56 -0700 Message-ID: <20170813092556.GA19019@infradead.org> References: <20170727131245.28279-1-jack@suse.cz> <20170727215713.GA22000@linux.intel.com> <20170728093821.GB29433@quack2.suse.cz> <20170801110241.GE6742@infradead.org> <20170801112603.GG4215@quack2.suse.cz> <20170811100327.GD7064@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Jan Kara , linux-nvdimm , Dave Chinner , linux-xfs@vger.kernel.org, Andy Lutomirski , Linux FS Devel , "linux-ext4@vger.kernel.org" To: Dan Williams Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Sat, Aug 12, 2017 at 07:44:14PM -0700, Dan Williams wrote: > How about MAP_SYNC == (MAP_SHARED|MAP_PRIVATE)? On older kernels that > should get -EINVAL, and on new kernels it means SYNC+SHARED. Cute trick, but I'd hate to waster it just for our little flag. How about: #define __MAP_VALIDATE MAP_SHARED|MAP_PRIVATE #define MAP_SYNC 0x??? | __MAP_VALIDATE so that we can reuse that trick for any new flag?