From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219306] ext4_truncate() is being called endlessly, all the time
Date: Wed, 25 Sep 2024 22:31:05 +0000 [thread overview]
Message-ID: <bug-219306-13602-I7DZxac5vn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219306-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219306
--- Comment #4 from Theodore Tso (tytso@mit.edu) ---
"Won't be called most of the time" is rather understating the case. The
WARN_ON should never, *EVER* fire. If it does we have a kernel bug, and if the
user has panic_on_warn set, the kernel will crash.
Also, please note that the WARN_ON would triggers when we have a inode-specific
inconsistency. In the extremely unlikely case that the WARN_ON triggers, the
doom loop that you are worried about would only happen if (a) panic_on_warn is
disabled, and (b) the inconsistent data state happens to be the journald's log
file. If the file system has millions of inodes, we're talking about a
probability of one in millions, even if the kernel is buggy and triggers at
all.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2024-09-25 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 11:38 [Bug 219306] New: ext4_truncate() is being called endlessly, all the time bugzilla-daemon
2024-09-24 15:08 ` [Bug 219306] " bugzilla-daemon
2024-09-25 0:10 ` bugzilla-daemon
2024-09-25 13:36 ` bugzilla-daemon
2024-09-25 22:31 ` bugzilla-daemon [this message]
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=bug-219306-13602-I7DZxac5vn@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).