From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 221570] [BUG] ext4: WARNING in dquot_reclaim_space_nodirty on bigalloc + PUNCH_HOLE
Date: Mon, 25 May 2026 01:41:52 +0000 [thread overview]
Message-ID: <bug-221570-13602-NevNGt71FK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221570-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221570
Theodore Tso (tytso@mit.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #3 from Theodore Tso (tytso@mit.edu) ---
When reporting these sorts of syzkaller bugs, please include the file system
image that was mounted in the VM.
The official upstream syzkaller has a way where you can download it from their
web interface. The problem with people running forked copies of syzkallers are
(a) often this is a duplicate of a bug already reported by the upstrea/official
syzkaller, and (b) without the web interface, looking at these bugs are much
more difficult.
Also note that if the file system image is corrupted (which is often the case
with Syzkaller), addressing these issues are a best efforts basis by the ext4
developers. Some company is going to fund an engineer to work on this on
official work time. Volunteers who have time on weekends or late at night
can't be expected to work these sorts of issues on anything other than a "best
efforts" basis.
--
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:[~2026-05-25 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 17:11 [Bug 221570] New: [BUG] ext4: WARNING in dquot_reclaim_space_nodirty on bigalloc + PUNCH_HOLE bugzilla-daemon
2026-05-24 17:12 ` [Bug 221570] " bugzilla-daemon
2026-05-24 17:12 ` bugzilla-daemon
2026-05-25 1:41 ` 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-221570-13602-NevNGt71FK@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