From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 703BCC77B7E for ; Mon, 24 Apr 2023 19:37:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232672AbjDXThZ (ORCPT ); Mon, 24 Apr 2023 15:37:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42738 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232453AbjDXThX (ORCPT ); Mon, 24 Apr 2023 15:37:23 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A9BAE5B88; Mon, 24 Apr 2023 12:37:22 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 3359462883; Mon, 24 Apr 2023 19:37:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 566D4C433B3; Mon, 24 Apr 2023 19:37:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1682365041; bh=YWbSyHY7pUE5AOb/3VWzPWd3sWsQ69Y7x41HE1Dt2f8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=kDBWBxcRX36vIRCPQdN4ZUSdbSHX1O4Pd+ZO4nc3vupupBHzNk5Dk91nuDsIQ1rOH TqW+/Qd/EiK0dYyV1/5FLrIBnUSpq7xs31OE+7UwRsA5LpC1j9OwF7djbzyJxgWSHk cTzUpSzsdO3OotdRptYWv3/TZvD6lEfUf01ojwlUPWNODt2ILOz0Uec1W97Nv2KpIK 2MP4gf/Xry+1mHMPMV0NAd9hTZgWH4WczEdoc62VroOonVWQQs1erBn2kICiokJEP7 PLFzocQ/KEmEsnnhZ4aDYS/btGy3oYDzDHqf6NvUrV/g4vv33mYH1BCgXtB4Gbp2FJ D0frIKzhrqALw== Date: Mon, 24 Apr 2023 13:37:18 -0600 From: Keith Busch To: Randy Dunlap Cc: Christoph Hellwig , Jens Axboe , Miklos Szeredi , "Darrick J. Wong" , Andrew Morton , David Howells , Matthew Wilcox , linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, cluster-devel@redhat.com, linux-xfs@vger.kernel.org, linux-nfs@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 02/17] fs: remove the special !CONFIG_BLOCK def_blk_fops Message-ID: References: <20230424054926.26927-1-hch@lst.de> <20230424054926.26927-3-hch@lst.de> <5f30b56e-b46b-1d3f-75fb-7f30ff6ca3e9@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5f30b56e-b46b-1d3f-75fb-7f30ff6ca3e9@infradead.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 24, 2023 at 12:22:30PM -0700, Randy Dunlap wrote: > On 4/23/23 22:49, Christoph Hellwig wrote: > > + if (IS_ENABLED(CONFIG_BLOCK)) > > + inode->i_fop = &def_blk_fops; > > It looks like def_blk_fops is being removed (commit message and patch > fragment below), but here (above line) it is being used. > > Am I just confused? The def_blk_fops is removed only for the !CONFIG_BLOCK case. Its usage is under a branch known at compile time, so it's optimized out for that case before trying to resolve the symbol.