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
| ||
|
Message-ID: <20230912235047.GA11463@frogsfrogsfrogs> Date: Tue, 12 Sep 2023 16:50:47 -0700 From: "Darrick J. Wong" <djwong@...nel.org> To: Theodore Ts'o <tytso@....edu> Cc: Sanan Hasanov <Sanan.Hasanov@....edu>, "adilger.kernel@...ger.ca" <adilger.kernel@...ger.ca>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "syzkaller@...glegroups.com" <syzkaller@...glegroups.com>, "contact@...zz.com" <contact@...zz.com> Subject: Re: general protection fault in ext4_update_overhead On Tue, Sep 12, 2023 at 07:41:12PM -0400, Theodore Ts'o wrote: > On Tue, Sep 12, 2023 at 11:02:35PM +0000, Sanan Hasanov wrote: > > Good day, dear maintainers, > > > > We found a bug using a modified kernel configuration file used by syzbot. > > > > We enhanced the coverage of the configuration file using our tool, klocalizer. > > > > Kernel Branch: 6.3.0-next-20230426 Also this was from ^^^^^^^^ four months ago. Why are you wasting Ted and everyone else's time with this? --D > > Kernel Config: https://drive.google.com/file/d/1xpe7qMUUYvHQFzqZGUzcco9jF97EwTqQ/view?usp=sharing > > Reproducer: https://drive.google.com/file/d/1Q8ix6EiWrzx0bWLyoGTHP721KE4Ei3qf/view?usp=sharing > > The reproducer is a zero-length file. So I can do nothing with this > report. > > Note that the official syzbot instance will do automatic bisection, > and will allow us to test patches. The official syzbot instance also > processes the console output so that the stack trace has line numbers > and clickable links to the kernel sources. > > This report is **much** less useful than the syzbot report, so please > don't be surprised if people treat this at a significantly lower > priority. (Even if the reproducer wasn't a zero length file. :-P ) > > - Ted
Powered by blists - more mailing lists