Hello,
syzbot found the following issue on:
HEAD commit: 8b723968 ext2fs: clear write cluster tracking on truncation
git tree:
https://github.com/freebsd/freebsd-src.git main
console output:
https://syzkaller.appspot.com/x/log.txt?x=163f78bcd00000
dashboard link:
https://syzkaller.appspot.com/bug?extid=2e35ed33b9b494e74b01
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+2e35ed...@syzkaller.appspotmail.com
SYZFAIL: tun: read failed
(errno 0: No error: 0)
SYZFAIL: child failed
if_delmulti_locked: detaching ifnet instance 0xfffff80019c5a800
if_delmulti_locked: detaching ifnet instance 0xfffff80019c5a800
if_delmulti_locked: detaching ifnet instance 0xfffff80019c5a800
if_delmulti_locked: detaching ifnet instance 0xfffff80019c5a800
if_delmulti_locked: detaching ifnet instance 0xfffff80019c5a800
if_delmulti_locked: detaching ifnet instance 0xfffff80019c5a800
if_delmulti_locked: detaching ifnet instance 0xfffff80019c5a800
if_delmulti_locked: detaching ifnet instance 0xfffff80019ab1000
if_delmulti_locked: detaching ifnet instance 0xfffff80019ab1000
if_delmulti_locked: detaching ifnet instance 0xfffff80019ab1000
Feb 21 18:03:48 ci-freebsd-main-3 dhclient[19348]: Interface tap1 is down, dhclient exiting
FreeBSD/amd64 (ci-freebsd-main-3.c.syzkaller.internal) (ttyu0)
login: if_delmulti_locked: detaching ifnet instance 0xfffff80019ab1800
if_delmulti_locked: detaching ifnet instance 0xfffff80019ab1800
if_delmulti_locked: detaching ifnet instance 0xfffff80019ab1800
Feb 21 18:03:49 ci-freebsd-main-3 dhclient[815]: Interface tap0 is down, dhclient exiting
Feb 21 18:03:49 ci-freebsd-main-3 dhclient[815]: connection closed
Feb 21 18:03:49 ci-freebsd-main-3 dhclient[815]: exiting.
if_delmulti_locked: detaching ifnet instance 0xfffff80019b77800
if_delmulti_locked: detaching ifnet instance 0xfffff80019b77800
if_delmulti_locked: detaching ifnet instance 0xfffff80019b77800
set $lines = 0
---
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.