From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH v5 4/5] fs, xfs: introduce MAP_DIRECT for creating block-map-atomic file ranges Date: Wed, 16 Aug 2017 09:32:48 -0700 Message-ID: References: <150286944610.8837.9513410258028246174.stgit@dwillia2-desk3.amr.corp.intel.com> <150286946864.8837.17147962029964281564.stgit@dwillia2-desk3.amr.corp.intel.com> <20170816111244.uxx6kvbi3cn5clqd@node.shutemov.name> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: owner-linux-mm@kvack.org To: "Kirill A. Shutemov" Cc: Andrew Morton , Jan Kara , "Darrick J. Wong" , Linux API , "linux-nvdimm@lists.01.org" , Dave Chinner , "linux-kernel@vger.kernel.org" , linux-xfs@vger.kernel.org, Linux MM , Jeff Moyer , Alexander Viro , Andy Lutomirski , linux-fsdevel , Ross Zwisler , Christoph Hellwig List-Id: linux-api@vger.kernel.org On Wed, Aug 16, 2017 at 9:29 AM, Dan Williams wrote: > On Wed, Aug 16, 2017 at 4:12 AM, Kirill A. Shutemov > wrote: >> On Wed, Aug 16, 2017 at 12:44:28AM -0700, Dan Williams wrote: >>> @@ -1411,6 +1422,9 @@ unsigned long do_mmap(struct file *file, unsigned long addr, >>> >>> /* fall through */ >>> case MAP_PRIVATE: >>> + if ((flags & (MAP_PRIVATE|MAP_DIRECT)) >>> + == (MAP_PRIVATE|MAP_DIRECT)) >>> + return -EINVAL; >> >> We've already checked for MAP_PRIVATE in this codepath. Simple (flags & >> MAP_DIRECT) would be enough. > > True, willl fix. Actually, no, because of the fallthrough we need to check MAP_SHARED or MAP_PRIVATE along with MAP_DIRECT. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org