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 D42B0C678DB for ; Tue, 7 Mar 2023 06:32:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230248AbjCGGcF (ORCPT ); Tue, 7 Mar 2023 01:32:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230240AbjCGGcE (ORCPT ); Tue, 7 Mar 2023 01:32:04 -0500 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 879E7515C3; Mon, 6 Mar 2023 22:32:03 -0800 (PST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id EA5675C0524; Tue, 7 Mar 2023 01:32:01 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 07 Mar 2023 01:32:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1678170721; x=1678257121; bh=JN NUYCnkXweyF5D43Jgpx00DAkQIyN+bBZ5xRNByPbw=; b=hhC07T/R3EcIqvvwgO QgpfqL8WBEBf4nvuFx34osznklLBKLAzpQRIOEL+pjc6KAOYl25YJZy7LNZx+fIT LkBCkN/2NKD0H0lZdPB7Siv4lqR4UJBuBge1UWxg/quaS8PFzpFh6KnKpg938wiF Em+A2HJwJErcaD4cf1Z4Wcxmc3xY/139QhlqriyXNHoXt3CnIYLfH92fwxigt4qW bQ2o/hJ2RnbG69FrqaP1pATivKG7ai2B1eur3MrqmjL9i6wprpuUcbXXafDdSVGs 4Piip54pS18Xtjmw5DhDzxyvJDLfooSD/tddcDTTkkJ2fvwozZt0NDd8zbDhYg/u 65jg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1678170721; x=1678257121; bh=JNNUYCnkXweyF 5D43Jgpx00DAkQIyN+bBZ5xRNByPbw=; b=QDZLX95UdgLVEslW0xYtV+fttAPGN pxAu+ELUXUjEqA7PmylTWA8p9v7gCaE1w8HZkpFv1uDcQWMPURjy9efLCJPzhzwu qAjx0MM/yEpkmCi5VReRx7WHICBjSiBl2j6i5JT+pHwxVVI7dYvN/0iZll7clzUZ xaiH0Vf287lClgl2e7kEx0+qvPE58kSDRYMniThImwcVMpSHW46JBcIGEqKJ6lwK M2uGlGVMFKe4OhIHE4odNB0oyO/jkD3GDcir/cS0HWd/+w00SxeKtlgUnCmF2tK+ k82QGaCPzw6qfHcJxovUmxUPq8WCCBiEzzRY+Atw5EhEJ8lUtJr/vFCWw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddtledgleehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepheegvd evvdeljeeugfdtudduhfekledtiefhveejkeejuefhtdeufefhgfehkeetnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorg hhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 7 Mar 2023 01:32:00 -0500 (EST) Date: Tue, 7 Mar 2023 07:31:57 +0100 From: Greg KH To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: runtime warning after merge of the driver-core tree Message-ID: References: <20230307134313.1b2aa555@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230307134313.1b2aa555@canb.auug.org.au> Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Tue, Mar 07, 2023 at 01:43:13PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the driver-core tree, today's linux-next qemu boot > (powerpc pseries_le_defconfig) produced this boot time warning: > > HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page > sysfs: cannot create duplicate filename '//block' That is odd. What type of userspace are you running this with? And is there a pointer to the .config anywhere? No one should be needing this old config option anymore, but maybe I messed something up in removing it... thanks, greg k-h