linux-kernel - Re: [Linux Kernel Bug] general protection fault in xfarray

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: <aXBeSQJdqtfvSC6u@casper.infradead.org>
Date: Wed, 21 Jan 2026 05:04:09 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Jiaming Zhang <r772577952@...il.com>
Cc: "Darrick J. Wong" <djwong@...nel.org>, cem@...nel.org,
	linux-xfs@...r.kernel.org, brauner@...nel.org,
	linux-kernel@...r.kernel.org, syzkaller@...glegroups.com
Subject: Re: [Linux Kernel Bug] general protection fault in xfarray_destroy

On Wed, Jan 21, 2026 at 12:58:58PM +0800, Jiaming Zhang wrote:
> Additionally, all reported issues were discovered by running syzkaller
> with our new generated syscall specs :) syzbot has not found these
> issues yet because the upstream instance currently lacks these specs.

Work with syzkaller upstream to get your changes into syzkaller.
It's far more productive, both for you and everybody else involved.
Don't be syzbot, you're not nearly as good at being syzbot as syzbot is.