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 AAADFC43334 for ; Tue, 7 Jun 2022 12:33:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243761AbiFGMdV (ORCPT ); Tue, 7 Jun 2022 08:33:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45024 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242695AbiFGMdS (ORCPT ); Tue, 7 Jun 2022 08:33:18 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 65E2C6D198; Tue, 7 Jun 2022 05:33:17 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 0B8A71F968; Tue, 7 Jun 2022 12:33:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1654605196; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=uf7X1P+eft8n9oLVYCmNH8QJXSIXiGGa7r7u8nKCitc=; b=EMI1NXVUQfGwxPLsSKYWQMJ5ZCBqj7rJKlkmNJDrH7q0XIOuz9UKMSDkxLwjm7nbDL8JBK HHTyLMF42yzpuX9ExVXtnN+tSWGFrsXK5bBTlzOZkwLdwoXoQOqTNKiV1c0rWWcAlsTZRN 9zZQcFTsZK2KglSQ+5TW+6bMYb1vFXg= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id C18F513A88; Tue, 7 Jun 2022 12:33:15 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id cxjULYtFn2LPDAAAMHmgww (envelope-from ); Tue, 07 Jun 2022 12:33:15 +0000 From: Juergen Gross To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Juergen Gross , Heiko Carstens , Vasily Gorbik , Alexander Gordeev , Christian Borntraeger , Sven Schnelle Subject: [PATCH] s390/kvm: avoid hypfs error message Date: Tue, 7 Jun 2022 14:33:14 +0200 Message-Id: <20220607123314.10255-1-jgross@suse.com> X-Mailer: git-send-email 2.35.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When booting under KVM the following error messages are issued: hypfs.7f5705: The hardware system does not support hypfs hypfs.7a79f0: Initialization of hypfs failed with rc=-61 While being documented, they can easily be avoided by bailing out of hypfs_init() early in case of running as a KVM guest. Signed-off-by: Juergen Gross --- arch/s390/hypfs/inode.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/s390/hypfs/inode.c b/arch/s390/hypfs/inode.c index 5c97f48cea91..bdf078f3c641 100644 --- a/arch/s390/hypfs/inode.c +++ b/arch/s390/hypfs/inode.c @@ -464,6 +464,9 @@ static int __init hypfs_init(void) { int rc; + if (MACHINE_IS_KVM) + return -ENODATA; + hypfs_dbfs_init(); if (hypfs_diag_init()) { -- 2.35.3