linux-kernel - Re: [syzbot] [ext4?] general protection fault in jbd2_journal_dirty

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAO9qdTFizqGeLakyFBFuLmr3EhDsdMRLeFS6AAEeXbFy2ZcffQ@mail.gmail.com>
Date: Tue, 13 May 2025 00:48:19 +0900
From: Jeongjun Park <aha310510@...il.com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: syzbot <syzbot+de24c3fe3c4091051710@...kaller.appspotmail.com>, 
	linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [ext4?] general protection fault in jbd2_journal_dirty_metadata

Theodore Ts'o <tytso@....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@...il.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.