Hi Ted, Syzkaller already tries to avoid such situations, but in this particular case, it has corrupted the mount options[1] and did not recognize the problem. Though, as I understand, this string was nevertheless valid to the kernel. Otherwise it would have aborted the mount early (?). I've sent a PR that should make the syzkaller logic more robust to such broken options strings: https://github.com/google/syzkaller/pull/3604 [1] grpjquota=Jnoinit_itable(errors=remount-ro,minixdf,jqfmt=vfsv0,usrjquota=." -- Aleksandr On Thu, Dec 29, 2022 at 12:14 AM Theodore Ts'o <tytso@xxxxxxx> wrote: > > So this is a totally bogus Syzbot report. If you use the mount option > "errors=panic", and you feed ext4 a corrupted file system, then it > *will* issue an "Ext4-fs error" message, and if you tell it to panic, > it will panic. > > So *please* let's not have some crazy Red Hat principal engineer try > to file this as a high severity CVE.... > > This is Working As Intended. And it is Not A Bug. > > - Ted > > -- > You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@xxxxxxxxxxxxxxxx. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/Y6zN/Q3glUcbty%2Bc%40mit.edu.
