From: cem@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [PATCH] xfs: Comment out unreachable code within xchk_fscounters()
Date: Tue, 6 Jun 2023 15:37:10 +0200 [thread overview]
Message-ID: <20230606133710.674706-1-cem@kernel.org> (raw)
From: Carlos Maiolino <cem@kernel.org>
Comment the code out so kernel test robot stop complaining about it
every single test build.
Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
---
fs/xfs/scrub/fscounters.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/xfs/scrub/fscounters.c b/fs/xfs/scrub/fscounters.c
index e382a35e98d88..b1148bea7fabc 100644
--- a/fs/xfs/scrub/fscounters.c
+++ b/fs/xfs/scrub/fscounters.c
@@ -452,6 +452,7 @@ xchk_fscounters(
*/
return 0;
+#if 0
/*
* If ifree exceeds icount by more than the minimum variance then
* something's probably wrong with the counters.
@@ -489,4 +490,5 @@ xchk_fscounters(
xchk_set_corrupt(sc);
return 0;
+#endif
}
--
2.30.2
next reply other threads:[~2023-06-06 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <T_8tV8A10oGZEuptzXoj3XFlD_-Ubqx0imHpEcDfSogB7Zfy2zaQhiSq2U9pkW3E65U6VKUJ46394RCv5lGGMA==@protonmail.internalid>
2023-06-06 13:37 ` cem [this message]
2023-06-06 13:43 ` [PATCH] xfs: Comment out unreachable code within xchk_fscounters() Carlos Maiolino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230606133710.674706-1-cem@kernel.org \
--to=cem@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox