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-next>] [day] [month] [year] [list]
Message-ID: <0000000000006f1f5d05b06394d0@google.com>
Date:   Mon, 28 Sep 2020 11:10:22 -0700
From:   syzbot <syzbot+2435de7315366e15f0ca@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: WARNING: filesystem loop1 was created with 512 inodes, the real
 maximum is 511, mounting anyway

Hello,

syzbot found the following issue on:

HEAD commit:    c9c9e6a4 Merge tag 'trace-v5.9-rc5-2' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=138b09d9900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5f4c828c9e3cef97
dashboard link: https://syzkaller.appspot.com/bug?extid=2435de7315366e15f0ca
compiler:       gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2435de7315366e15f0ca@...kaller.appspotmail.com

BFS-fs: bfs_fill_super(): WARNING: filesystem loop1 was created with 512 inodes, the real maximum is 511, mounting anyway
BFS-fs: bfs_fill_super(): Inode 0x00000002 corrupted on loop1
BFS-fs: bfs_fill_super(): WARNING: filesystem loop1 was created with 512 inodes, the real maximum is 511, mounting anyway
BFS-fs: bfs_fill_super(): Inode 0x00000002 corrupted on loop1


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ