From: bugzilla-daemon--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 203861] Division by zero error in fsck.f2fs when fixing a corrupted image
Date: Sun, 10 May 2026 08:47:27 +0000 [thread overview]
Message-ID: <bug-203861-202145-CFUJ3Ank6N@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203861-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203861
Attila (cs.attila@zerodaybugs.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cs.attila@zerodaybugs.com
--- Comment #4 from Attila (cs.attila@zerodaybugs.com) ---
Current-master fsck.f2fs reproducer package for Bug 203861: ASAN/UBSAN log,
evidence card, concept fix, mount.c context, and minimized crash artifacts
showing SIGFPE in sanity_check_raw_super() with secs_per_zone=0 / derived
segs_per_zone=0.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-05-10 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 18:17 [Bug 203861] New: Division by zero error in fsck.f2fs when fixing a corrupted image bugzilla-daemon
2019-06-10 18:17 ` [f2fs-dev] " bugzilla-daemon
2019-07-11 1:10 ` [f2fs-dev] [Bug 203861] " bugzilla-daemon
2019-07-15 7:39 ` bugzilla-daemon
2019-07-15 8:08 ` bugzilla-daemon
2026-05-10 8:47 ` bugzilla-daemon--- via Linux-f2fs-devel [this message]
2026-05-10 8:48 ` bugzilla-daemon--- via Linux-f2fs-devel
2026-05-10 8:55 ` bugzilla-daemon--- via Linux-f2fs-devel
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-203861-202145-CFUJ3Ank6N@https.bugzilla.kernel.org/ \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bugzilla-daemon@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