[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170813092556.GA19019@infradead.org>
Date: Sun, 13 Aug 2017 02:25:56 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Christoph Hellwig <hch@...radead.org>, Jan Kara <jack@...e.cz>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
Dave Chinner <david@...morbit.com>, linux-xfs@...r.kernel.org,
Andy Lutomirski <luto@...nel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: [RFC PATCH 0/7] dax, ext4: Synchronous page faults
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?
Powered by blists - more mailing lists