From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com ([192.55.52.115]:11611 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753284AbcK1VYW (ORCPT ); Mon, 28 Nov 2016 16:24:22 -0500 Date: Mon, 28 Nov 2016 14:24:00 -0700 From: Ross Zwisler To: Arnd Bergmann Cc: Theodore Ts'o , Ross Zwisler , Alexander Viro , Matthew Wilcox , Jan Kara , Andrew Morton , Dave Chinner , Dan Williams , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] dax: try to avoid unused function warnings Message-ID: <20161128212400.GA16225@linux.intel.com> References: <20161128211233.2446605-1-arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20161128211233.2446605-1-arnd@arndb.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Nov 28, 2016 at 10:12:17PM +0100, Arnd Bergmann wrote: > Without the get_block based I/O, we get warnings when CONFIG_FS_IOMAP > is disabled: > > fs/dax.c:736:12: error: ‘dax_insert_mapping’ defined but not used [-Werror=unused-function] > fs/dax.c:512:12: error: ‘copy_user_dax’ defined but not used [-Werror=unused-function] > fs/dax.c:490:12: error: ‘dax_load_hole’ defined but not used [-Werror=unused-function] > fs/dax.c:294:14: error: ‘grab_mapping_entry’ defined but not used [-Werror=unused-function] > > This patch blindly marks those as __maybe_unused, which avoids the warnings. > However, I suspect that there is actually more code in this file that should > not be provided without CONFIG_FS_IOMAP even though we don't get a warning > for it, and that we actually want a different rework, so please treat this > as a bug report. I have applied the patch locally in my randconfig build > setup to avoid seeing the warnings. > > Fixes: 5ac65736f740 ("dax: rip out get_block based IO support") > Signed-off-by: Arnd Bergmann Thanks for the report. I think the right way to deal with this is to just select FS_IOMAP when we pull in the DAX code. I sent out a patch last week that does this: https://lkml.org/lkml/2016/11/23/591