From: Avinesh Kumar <avinesh.kumar@suse.com>
To: linux-xfs@vger.kernel.org
Cc: fstests@vger.kernel.org, djwong@kernel.org, cem@kernel.org
Subject: [RFC PATCH] libfrog: make cmn_err() emit each message atomically to avoid torn output
Date: Wed, 15 Jul 2026 19:28:21 +0200 [thread overview]
Message-ID: <20260715173114.359368-1-avinesh.kumar@suse.com> (raw)
From: Avinesh Kumar <avinesh.kumar@suse.com>
fstests xfs/033 fails sporadically with a spurious blank line in the
xfs_repair output:
- output mismatch (see /opt/xfstests/results//xfs/033.out.bad)
--- tests/xfs/033.out 2026-06-24 15:52:51.000000000 -0400
+++ /opt/xfstests/results//xfs/033.out.bad 2026-07-14 18:54:46.582495041 -0400
@@ -103,6 +103,7 @@
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
+
bad magic number 0xffff on inode INO
bad version number 0xffffffff on inode INO
inode identifier 18446744073709551615 mismatch on inode INO
Root cause is in cmn_err() (libfrog/util.c), which emits a message
and its newline as two separate writes to unbuffered stderr.
xfs_repair's threads all share stderr. If one is preempted between the
two writes, another thread's line lands in between:
(snips from `cat -A 033.raw`) -
Phase 3 - for each AG...$
- scan and clear agi unlinked lists...$
- process known inodes and perform inode discovery...$
Metadata corruption detected at 0x445dd3, xfs_inode block 0x80/0x4000 - agno = 0$
$
bad CRC for inode 128$
bad magic number 0x0 on inode 128$
which should be like -
Phase 3 - for each AG...$
- scan and clear agi unlinked lists...$
- process known inodes and perform inode discovery...$
Metadata corruption detected at 0x445dd3, xfs_inode block 0x80/0x4000$
- agno = 0$
bad CRC for inode 130$
bad magic number 0x0 on inode 130$
_filter_repair() strips the noise line it glued onto but not the lone
newline, which then fails the golden diff.
Make the two writes atomic.
Signed-off-by: Avinesh Kumar <avinesh.kumar@suse.com>
---
Hi, please give feedback if this should be fixed in a different way.
Thanks!
libfrog/util.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libfrog/util.c b/libfrog/util.c
index 5bae5bab..3b6df917 100644
--- a/libfrog/util.c
+++ b/libfrog/util.c
@@ -116,8 +116,10 @@ cmn_err(int level, char *fmt, ...)
va_list ap;
va_start(ap, fmt);
+ flockfile(stderr);
vfprintf(stderr, fmt, ap);
fputs("\n", stderr);
+ funlockfile(stderr);
va_end(ap);
}
--
2.55.0
next reply other threads:[~2026-07-15 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 17:28 Avinesh Kumar [this message]
2026-07-15 19:09 ` [RFC PATCH] libfrog: make cmn_err() emit each message atomically to avoid torn output Darrick J. Wong
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=20260715173114.359368-1-avinesh.kumar@suse.com \
--to=avinesh.kumar@suse.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.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