From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1CF3881EB2 for ; Tue, 29 Nov 2016 00:53:09 -0800 (PST) Date: Tue, 29 Nov 2016 09:53:03 +0100 From: Jan Kara Subject: Re: [PATCH 1/6] dax: fix build breakage with ext4, dax and !iomap Message-ID: <20161129085303.GA7550@quack2.suse.cz> References: <1479926662-21718-1-git-send-email-ross.zwisler@linux.intel.com> <1479926662-21718-2-git-send-email-ross.zwisler@linux.intel.com> <20161124090239.GA24138@quack2.suse.cz> <20161128191504.GB6637@linux.intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20161128191504.GB6637@linux.intel.com> 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: Ross Zwisler Cc: Jan Kara , Matthew Wilcox , Dave Chinner , linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, Steven Rostedt , linux-mm@kvack.org, Ingo Molnar , Alexander Viro , linux-fsdevel@vger.kernel.org, Andrew Morton , linux-ext4@vger.kernel.org, Christoph Hellwig List-ID: On Mon 28-11-16 12:15:04, Ross Zwisler wrote: > On Thu, Nov 24, 2016 at 10:02:39AM +0100, Jan Kara wrote: > > On Wed 23-11-16 11:44:17, Ross Zwisler wrote: > > > With the current Kconfig setup it is possible to have the following: > > > > > > CONFIG_EXT4_FS=y > > > CONFIG_FS_DAX=y > > > CONFIG_FS_IOMAP=n # this is in fs/Kconfig & isn't user accessible > > > > > > With this config we get build failures in ext4_dax_fault() because the > > > iomap functions in fs/dax.c are missing: > > > > > > fs/built-in.o: In function `ext4_dax_fault': > > > file.c:(.text+0x7f3ac): undefined reference to `dax_iomap_fault' > > > file.c:(.text+0x7f404): undefined reference to `dax_iomap_fault' > > > fs/built-in.o: In function `ext4_file_read_iter': > > > file.c:(.text+0x7fc54): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_file_write_iter': > > > file.c:(.text+0x7fe9a): undefined reference to `dax_iomap_rw' > > > file.c:(.text+0x7feed): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_block_zero_page_range': > > > inode.c:(.text+0x85c0d): undefined reference to `iomap_zero_range' > > > > > > Now that the struct buffer_head based DAX fault paths and I/O path have > > > been removed we really depend on iomap support being present for DAX. Make > > > this explicit by selecting FS_IOMAP if we compile in DAX support. > > > > > > Signed-off-by: Ross Zwisler > > > > I've sent the same patch to Ted yesterday and he will probably queue it on > > top of ext4 iomap patches. If it doesn't happen for some reason, feel free > > to add: > > > > Reviewed-by: Jan Kara > > Cool, looks like Ted has pulled in your patch. > > I think we still eventually want this patch because it cleans up our handling > of FS_IOMAP. With your patch we select it separately in both ext4 & ext2 > based on whether we include DAX, and we still have #ifdefs in fs/dax.c for > FS_IOMAP. Actually, based on Dave's request I've also sent Ted updated version which did select FS_IOMAP in CONFIG_DAX section. However Ted didn't pull that patch (yet?). Anyway, I don't care whose patch gets merged, I just wanted to notify you of possible conflict. Honza -- Jan Kara SUSE Labs, CR _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933169AbcK2IxP (ORCPT ); Tue, 29 Nov 2016 03:53:15 -0500 Received: from mx2.suse.de ([195.135.220.15]:46581 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753904AbcK2IxJ (ORCPT ); Tue, 29 Nov 2016 03:53:09 -0500 Date: Tue, 29 Nov 2016 09:53:03 +0100 From: Jan Kara To: Ross Zwisler Cc: Jan Kara , linux-kernel@vger.kernel.org, Alexander Viro , Andrew Morton , Christoph Hellwig , Dan Williams , Dave Chinner , Ingo Molnar , Matthew Wilcox , Steven Rostedt , linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@ml01.01.org Subject: Re: [PATCH 1/6] dax: fix build breakage with ext4, dax and !iomap Message-ID: <20161129085303.GA7550@quack2.suse.cz> References: <1479926662-21718-1-git-send-email-ross.zwisler@linux.intel.com> <1479926662-21718-2-git-send-email-ross.zwisler@linux.intel.com> <20161124090239.GA24138@quack2.suse.cz> <20161128191504.GB6637@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161128191504.GB6637@linux.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 28-11-16 12:15:04, Ross Zwisler wrote: > On Thu, Nov 24, 2016 at 10:02:39AM +0100, Jan Kara wrote: > > On Wed 23-11-16 11:44:17, Ross Zwisler wrote: > > > With the current Kconfig setup it is possible to have the following: > > > > > > CONFIG_EXT4_FS=y > > > CONFIG_FS_DAX=y > > > CONFIG_FS_IOMAP=n # this is in fs/Kconfig & isn't user accessible > > > > > > With this config we get build failures in ext4_dax_fault() because the > > > iomap functions in fs/dax.c are missing: > > > > > > fs/built-in.o: In function `ext4_dax_fault': > > > file.c:(.text+0x7f3ac): undefined reference to `dax_iomap_fault' > > > file.c:(.text+0x7f404): undefined reference to `dax_iomap_fault' > > > fs/built-in.o: In function `ext4_file_read_iter': > > > file.c:(.text+0x7fc54): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_file_write_iter': > > > file.c:(.text+0x7fe9a): undefined reference to `dax_iomap_rw' > > > file.c:(.text+0x7feed): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_block_zero_page_range': > > > inode.c:(.text+0x85c0d): undefined reference to `iomap_zero_range' > > > > > > Now that the struct buffer_head based DAX fault paths and I/O path have > > > been removed we really depend on iomap support being present for DAX. Make > > > this explicit by selecting FS_IOMAP if we compile in DAX support. > > > > > > Signed-off-by: Ross Zwisler > > > > I've sent the same patch to Ted yesterday and he will probably queue it on > > top of ext4 iomap patches. If it doesn't happen for some reason, feel free > > to add: > > > > Reviewed-by: Jan Kara > > Cool, looks like Ted has pulled in your patch. > > I think we still eventually want this patch because it cleans up our handling > of FS_IOMAP. With your patch we select it separately in both ext4 & ext2 > based on whether we include DAX, and we still have #ifdefs in fs/dax.c for > FS_IOMAP. Actually, based on Dave's request I've also sent Ted updated version which did select FS_IOMAP in CONFIG_DAX section. However Ted didn't pull that patch (yet?). Anyway, I don't care whose patch gets merged, I just wanted to notify you of possible conflict. Honza -- Jan Kara SUSE Labs, CR From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 29 Nov 2016 09:53:03 +0100 From: Jan Kara To: Ross Zwisler Cc: Jan Kara , linux-kernel@vger.kernel.org, Alexander Viro , Andrew Morton , Christoph Hellwig , Dan Williams , Dave Chinner , Ingo Molnar , Matthew Wilcox , Steven Rostedt , linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@lists.01.org Subject: Re: [PATCH 1/6] dax: fix build breakage with ext4, dax and !iomap Message-ID: <20161129085303.GA7550@quack2.suse.cz> References: <1479926662-21718-1-git-send-email-ross.zwisler@linux.intel.com> <1479926662-21718-2-git-send-email-ross.zwisler@linux.intel.com> <20161124090239.GA24138@quack2.suse.cz> <20161128191504.GB6637@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161128191504.GB6637@linux.intel.com> Sender: owner-linux-mm@kvack.org List-ID: On Mon 28-11-16 12:15:04, Ross Zwisler wrote: > On Thu, Nov 24, 2016 at 10:02:39AM +0100, Jan Kara wrote: > > On Wed 23-11-16 11:44:17, Ross Zwisler wrote: > > > With the current Kconfig setup it is possible to have the following: > > > > > > CONFIG_EXT4_FS=y > > > CONFIG_FS_DAX=y > > > CONFIG_FS_IOMAP=n # this is in fs/Kconfig & isn't user accessible > > > > > > With this config we get build failures in ext4_dax_fault() because the > > > iomap functions in fs/dax.c are missing: > > > > > > fs/built-in.o: In function `ext4_dax_fault': > > > file.c:(.text+0x7f3ac): undefined reference to `dax_iomap_fault' > > > file.c:(.text+0x7f404): undefined reference to `dax_iomap_fault' > > > fs/built-in.o: In function `ext4_file_read_iter': > > > file.c:(.text+0x7fc54): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_file_write_iter': > > > file.c:(.text+0x7fe9a): undefined reference to `dax_iomap_rw' > > > file.c:(.text+0x7feed): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_block_zero_page_range': > > > inode.c:(.text+0x85c0d): undefined reference to `iomap_zero_range' > > > > > > Now that the struct buffer_head based DAX fault paths and I/O path have > > > been removed we really depend on iomap support being present for DAX. Make > > > this explicit by selecting FS_IOMAP if we compile in DAX support. > > > > > > Signed-off-by: Ross Zwisler > > > > I've sent the same patch to Ted yesterday and he will probably queue it on > > top of ext4 iomap patches. If it doesn't happen for some reason, feel free > > to add: > > > > Reviewed-by: Jan Kara > > Cool, looks like Ted has pulled in your patch. > > I think we still eventually want this patch because it cleans up our handling > of FS_IOMAP. With your patch we select it separately in both ext4 & ext2 > based on whether we include DAX, and we still have #ifdefs in fs/dax.c for > FS_IOMAP. Actually, based on Dave's request I've also sent Ted updated version which did select FS_IOMAP in CONFIG_DAX section. However Ted didn't pull that patch (yet?). Anyway, I don't care whose patch gets merged, I just wanted to notify you of possible conflict. Honza -- Jan Kara SUSE Labs, CR -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kara Subject: Re: [PATCH 1/6] dax: fix build breakage with ext4, dax and !iomap Date: Tue, 29 Nov 2016 09:53:03 +0100 Message-ID: <20161129085303.GA7550@quack2.suse.cz> References: <1479926662-21718-1-git-send-email-ross.zwisler@linux.intel.com> <1479926662-21718-2-git-send-email-ross.zwisler@linux.intel.com> <20161124090239.GA24138@quack2.suse.cz> <20161128191504.GB6637@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Jan Kara , Matthew Wilcox , Dave Chinner , linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Steven Rostedt , linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, Ingo Molnar , Alexander Viro , linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andrew Morton , linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Christoph Hellwig To: Ross Zwisler Return-path: Content-Disposition: inline In-Reply-To: <20161128191504.GB6637-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" List-Id: linux-ext4.vger.kernel.org On Mon 28-11-16 12:15:04, Ross Zwisler wrote: > On Thu, Nov 24, 2016 at 10:02:39AM +0100, Jan Kara wrote: > > On Wed 23-11-16 11:44:17, Ross Zwisler wrote: > > > With the current Kconfig setup it is possible to have the following: > > > > > > CONFIG_EXT4_FS=y > > > CONFIG_FS_DAX=y > > > CONFIG_FS_IOMAP=n # this is in fs/Kconfig & isn't user accessible > > > > > > With this config we get build failures in ext4_dax_fault() because the > > > iomap functions in fs/dax.c are missing: > > > > > > fs/built-in.o: In function `ext4_dax_fault': > > > file.c:(.text+0x7f3ac): undefined reference to `dax_iomap_fault' > > > file.c:(.text+0x7f404): undefined reference to `dax_iomap_fault' > > > fs/built-in.o: In function `ext4_file_read_iter': > > > file.c:(.text+0x7fc54): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_file_write_iter': > > > file.c:(.text+0x7fe9a): undefined reference to `dax_iomap_rw' > > > file.c:(.text+0x7feed): undefined reference to `dax_iomap_rw' > > > fs/built-in.o: In function `ext4_block_zero_page_range': > > > inode.c:(.text+0x85c0d): undefined reference to `iomap_zero_range' > > > > > > Now that the struct buffer_head based DAX fault paths and I/O path have > > > been removed we really depend on iomap support being present for DAX. Make > > > this explicit by selecting FS_IOMAP if we compile in DAX support. > > > > > > Signed-off-by: Ross Zwisler > > > > I've sent the same patch to Ted yesterday and he will probably queue it on > > top of ext4 iomap patches. If it doesn't happen for some reason, feel free > > to add: > > > > Reviewed-by: Jan Kara > > Cool, looks like Ted has pulled in your patch. > > I think we still eventually want this patch because it cleans up our handling > of FS_IOMAP. With your patch we select it separately in both ext4 & ext2 > based on whether we include DAX, and we still have #ifdefs in fs/dax.c for > FS_IOMAP. Actually, based on Dave's request I've also sent Ted updated version which did select FS_IOMAP in CONFIG_DAX section. However Ted didn't pull that patch (yet?). Anyway, I don't care whose patch gets merged, I just wanted to notify you of possible conflict. Honza -- Jan Kara SUSE Labs, CR