From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Liu Wenqing <wenqingliu0120@gmail.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Meet New meeting Join a meeting Hangouts 1 of 42 Page fault in fs/ext4/namei.c: do_split when crafted image is mounted and operated
Date: Sun, 5 Dec 2021 15:43:27 -0500 [thread overview]
Message-ID: <Ya0kbx3qZCeqFRnL@mit.edu> (raw)
In-Reply-To: <CA+AJg7OHrVgbHuRi5Sqyt5v1PzN-OhG8NjKaanLY-_+OZPvkDA@mail.gmail.com>
On Sat, Dec 04, 2021 at 01:33:29PM -0500, Liu Wenqing wrote:
> Hi,
>
> I have found a bug with our fuzzer, attached is the image, poc file and the
> .config file and the details are as follows.
Even though this has a later timestamp, this looks like a duplicate of
an earlier report, but with a mangled subject line?
- Ted
parent reply other threads:[~2021-12-05 20:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+AJg7OHrVgbHuRi5Sqyt5v1PzN-OhG8NjKaanLY-_+OZPvkDA@mail.gmail.com>]
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=Ya0kbx3qZCeqFRnL@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wenqingliu0120@gmail.com \
/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).