From: Jeongjun Park <aha310510@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: syzbot <syzbot+de24c3fe3c4091051710@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] general protection fault in jbd2_journal_dirty_metadata
Date: Tue, 13 May 2025 00:48:19 +0900 [thread overview]
Message-ID: <CAO9qdTFizqGeLakyFBFuLmr3EhDsdMRLeFS6AAEeXbFy2ZcffQ@mail.gmail.com> (raw)
In-Reply-To: <20250512150134.GB200944@mit.edu>
Theodore Ts'o <tytso@mit.edu> wrote:
>
> On Mon, May 12, 2025 at 07:46:08AM -0700, syzbot wrote:
> > > #syz test https://asdf asdf"></a>)('"><;
> >
> > "asdf\"></a>)('\"><;" does not look like a valid git branch or commit.
> >
>
> It looks like this was a reply to Jeongjun Park's request (in
> Message-Id: <20250512141322.15270-1-aha310510@gmail.com>):
>
> #syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> Or at least, his #syz test was sent less than 30 minutes before this
> reply; and syzbot didn't respond to his #syz test; and his #syz test
> request was a plain text e-mail without any text/plain vs text/html
> hijinks (I checked).
>
> Maybe someone in syzbot land can investigate?
>
> - Ted
Oh I’m truly sorry. While drafting a test patch, I got bored and started
playing around typing any things into the syzkaller HTML file and patch
file and I accidentally send this email.
I had absolutely no intention of attack LKML or syzbot.
I apologize for any confusion this may have caused.
next prev parent reply other threads:[~2025-05-12 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250512144602.15519-1-aha310510@gmail.com>
2025-05-12 14:46 ` syzbot
2025-05-12 15:01 ` Theodore Ts'o
2025-05-12 15:48 ` Jeongjun Park [this message]
2025-05-16 18:45 ` syzbot
2025-04-27 8:21 syzbot
2025-05-12 14:13 ` Jeongjun Park
2025-05-16 18:24 ` syzbot
2025-05-12 15:58 ` Jeongjun Park
2025-05-16 19:05 ` syzbot
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=CAO9qdTFizqGeLakyFBFuLmr3EhDsdMRLeFS6AAEeXbFy2ZcffQ@mail.gmail.com \
--to=aha310510@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+de24c3fe3c4091051710@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®