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: Sun, 26 Dec 2021 00:00:29 +0000 [thread overview]
Message-ID: <bug-215225-13602-vOPdehbmNy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215225-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215225
Wenqing Liu (wenqingliu0120@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wenqingliu0120@gmail.com
--- Comment #2 from Wenqing Liu (wenqingliu0120@gmail.com) ---
Created attachment 300157
--> https://bugzilla.kernel.org/attachment.cgi?id=300157&action=edit
POC_script
--
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-26 0:00 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 ` [Bug 215225] " bugzilla-daemon
2021-12-26 0:00 ` bugzilla-daemon [this message]
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-vOPdehbmNy@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 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).