From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aserp2120.oracle.com (aserp2120.oracle.com [141.146.126.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id BF1FF2265A172 for ; Tue, 17 Apr 2018 10:50:38 -0700 (PDT) Date: Tue, 17 Apr 2018 10:50:07 -0700 From: "Darrick J. Wong" Subject: Re: ioctl FIBMAP for dax gone in v4.17-rc1 Message-ID: <20180417175007.GB5210@magnolia> References: <20180417144059.nwbbynhgq3k3i63q@XZHOUW.usersys.redhat.com> <20180417161056.GA24257@infradead.org> <20180417165756.GC24738@magnolia> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Andreas Dilger Cc: linux-xfs , linux-nvdimm , Eric Sandeen , fstests , Christoph Hellwig , linux-fsdevel List-ID: On Tue, Apr 17, 2018 at 11:40:00AM -0600, Andreas Dilger wrote: > On Apr 17, 2018, at 10:57 AM, Darrick J. Wong wrote: > > > > On Tue, Apr 17, 2018 at 09:53:47AM -0700, Dan Williams wrote: > >> On Tue, Apr 17, 2018 at 9:10 AM, Christoph Hellwig wrote: > >>> On Tue, Apr 17, 2018 at 10:40:59PM +0800, Xiong Zhou wrote: > >>>> We got these in v4.17-rc1: > >>>> 6e2608d xfs, dax: introduce xfs_dax_aops > >>>> fb094c9 ext2, dax: introduce ext2_dax_aops > >>>> 5f0663b ext4, dax: introduce ext4_dax_aops > >>>> > >>>> And we don't have ->bmap call in these aops, which may lead > >>>> to the ioctl call failure. > >>>> > >>>> Do we have any plan of adding/supporting it ? > >>>> > >>>> xfstests generic/223 covers this issue. If we are not going > >>>> to support this call for dax, we need to fix the testcase. > >>> > >>> Not supporting ->bmap is a good thing as it is hightly dangerous. > >> > >> I take this to mean "don't fix, it is another casualty of dax being > >> experimental and it won't be coming back". I can get on board with > >> that. > >> > >> Otherwise, I was about to send a series adding bmap to {xfs,ext2,ext4}_dax_ops. > > > > Frankly I'd rather see the swapfile code learn how to iomap and then we > > can get rid of bmap in xfs entirely. > > Is anyone still using LILO to boot? It needed FIBMAP support to map the > kernel image for booting. I don't know if Grub needs FIBMAP support for > the early boot stages or not (it has minimal filesystem support in the > later stages), but it would be a shame if it wasn't possible to boot an > all-NVRAM system as a result of a missing ->bmap() method. Alternately, > convince the Grub folks to use FIEMAP if that is available... grub2 usually uses its own fs drivers (for better or for worse) to read the fs. The blockchaining mode tries FIEMAP and falls back to FIBMAP if not available. syslinux does FIEMAP w/ FIBMAP fallback. lilo & elilo still use FIBMAP only, but lilo hasn't seen a release since 2015 and elilo 2013. I prefer not to add FIBMAP support in XFS-DAX for the singular case of booting off pmem via lilo. (Sorry Dave...) --D > > Cheers, Andreas > > > > > _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm