From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 215225] FUZZ: Page fault and infinite loop after mount and operate on crafted image
Date: Fri, 24 Dec 2021 21:50:06 +0000 [thread overview]
Message-ID: <bug-215225-13602-bwS1Tocgi0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215225-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215225
Qinghua Jin (qhjin_dev@163.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qhjin_dev@163.com
--- Comment #1 from Qinghua Jin (qhjin_dev@163.com) ---
It seems that the tmp38.img is corrupt. Could you please send a correct one?
$ e2fsck tmp38.img
e2fsck 1.45.7 (28-Jan-2021)
ext2fs_open2: The ext2 superblock is corrupt
e2fsck: Superblock invalid, trying backup blocks...
tmp38.img contains a file system with errors, check forced.
Resize inode not valid. Recreate<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Root inode has dtime set (probably due to old mke2fs). Fix<y>? yes
Inode 13 has an invalid extent
(logical block 0, invalid physical block 8332801, len 1)
Clear<y>? yes
Inode 13 has an invalid extent
(logical block 0, invalid physical block 64344, len 1)
Clear<y>? yes
Thanks,
Qinghua Jin
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-12-24 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 20:36 [Bug 215225] New: FUZZ: Page fault and infinite loop after mount and operate on crafted image bugzilla-daemon
2021-12-24 21:50 ` bugzilla-daemon [this message]
2021-12-26 0:00 ` [Bug 215225] " bugzilla-daemon
2021-12-26 0:03 ` bugzilla-daemon
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-215225-13602-bwS1Tocgi0@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.