WARNING: the mand mount option is being deprecated and
187 views
Skip to first unread message
syzbot
Aug 26, 2021, 9:41:21 AM8/26/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e23d55af0e1f Linux 4.19.205
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14d83185300000
kernel config: https://syzkaller.appspot.com/x/.config?x=2221dd564152b412
dashboard link: https://syzkaller.appspot.com/bug?extid=ee9010508e9179091666
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
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+ee9010...@syzkaller.appspotmail.com
======================================================
WARNING: the mand mount option is being deprecated and
will be removed in v5.15!
======================================================
IPVS: ftp: loaded support on port[0] = 21
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
syz-executor.5 (14277) used greatest stack depth: 22264 bytes left
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
syz-executor.5 (14392) used greatest stack depth: 22176 bytes left
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
syz-executor.0 (14473) used greatest stack depth: 22160 bytes left
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
syz-executor.4 (14551) used greatest stack depth: 21864 bytes left
IPVS: ftp: loaded support on port[0] = 21
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPVS: ftp: loaded support on port[0] = 21
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
net_ratelimit: 3 callbacks suppressed
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
---
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.
syzbot found the following issue on:
HEAD commit: e23d55af0e1f Linux 4.19.205
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14d83185300000
kernel config: https://syzkaller.appspot.com/x/.config?x=2221dd564152b412
dashboard link: https://syzkaller.appspot.com/bug?extid=ee9010508e9179091666
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
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+ee9010...@syzkaller.appspotmail.com
======================================================
WARNING: the mand mount option is being deprecated and
will be removed in v5.15!
======================================================
IPVS: ftp: loaded support on port[0] = 21
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
EXT4-fs (sda1): Ignoring removed nobh option
EXT4-fs (sda1): re-mounted. Opts: nobh,,errors=continue
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
syz-executor.5 (14277) used greatest stack depth: 22264 bytes left
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
syz-executor.5 (14392) used greatest stack depth: 22176 bytes left
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
syz-executor.0 (14473) used greatest stack depth: 22160 bytes left
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
syz-executor.4 (14551) used greatest stack depth: 21864 bytes left
IPVS: ftp: loaded support on port[0] = 21
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
A link change request failed with some changes committed already. Interface caif0 may have been left with an inconsistent configuration, please check.
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
IPVS: ftp: loaded support on port[0] = 21
IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready
net_ratelimit: 3 callbacks suppressed
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
A link change request failed with some changes committed already. Interface gretap0 may have been left with an inconsistent configuration, please check.
IPVS: ftp: loaded support on port[0] = 21
---
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.
syzbot
Aug 26, 2021, 10:13:20 AM8/26/21
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 35c4ba160ab6 Linux 4.14.245
syzbot found the following issue on:
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=125ab239300000
kernel config: https://syzkaller.appspot.com/x/.config?x=95375411c1569761
dashboard link: https://syzkaller.appspot.com/bug?extid=df212363ff2a837256c3
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
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+df2123...@syzkaller.appspotmail.com
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:
IPv6: ADDRCONF(NETDEV_UP): veth1_virt_wifi: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_virt_wifi: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_virt_wifi: link becomes ready
IPv6: ADDRCONF(NETDEV_UP): veth0_virt_wifi: link is not ready
======================================================
WARNING: the mand mount option is being deprecated and
will be removed in v5.15!
======================================================
IPv6: ADDRCONF(NETDEV_UP): veth1_virt_wifi: link is not ready
WARNING: the mand mount option is being deprecated and
will be removed in v5.15!
======================================================
ceph: No mds server is up or the cluster is laggy
IPv6: ADDRCONF(NETDEV_UP): veth0_vlan: link is not ready
FAT-fs (loop2): bogus number of reserved sectors
IPv6: ADDRCONF(NETDEV_UP): vlan0: link is not ready
FAT-fs (loop2): Can't find a valid FAT filesystem
IPv6: ADDRCONF(NETDEV_UP): vlan1: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_virt_wifi: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_virt_wifi: link becomes ready
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
IPv6: ADDRCONF(NETDEV_UP): veth1_vlan: link is not ready
IPVS: ftp: loaded support on port[0] = 21
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_vlan: link becomes ready
libceph: mon0 [d::]:6789 connect error
FAT-fs (loop2): bogus number of reserved sectors
FAT-fs (loop2): Can't find a valid FAT filesystem
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_vlan: link becomes ready
device veth0_vlan entered promiscuous mode
IPv6: ADDRCONF(NETDEV_CHANGE): vlan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vlan1: link becomes ready
WARNING: can't dereference registers at 0000000000000943 for ip entry_SYSCALL_64_after_hwframe+0x46/0xbb
libceph: connect [d::]:6789 error -101
device veth1_vlan entered promiscuous mode
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
IPv6: ADDRCONF(NETDEV_UP): macvlan0: link is not ready
ceph: No mds server is up or the cluster is laggy
libceph: mon0 [d::]:6789 connect error
IPv6: ADDRCONF(NETDEV_UP): macvlan1: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth0_vlan: link is not ready
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
IPv6: ADDRCONF(NETDEV_UP): vlan0: link is not ready
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
IPv6: ADDRCONF(NETDEV_UP): vlan1: link is not ready
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
IPv6: ADDRCONF(NETDEV_UP): veth0_macvtap: link is not ready
libceph: mon0 [d::]:6789 connect error
input: syz1 as /devices/virtual/input/input5
IPv6: ADDRCONF(NETDEV_UP): veth1_vlan: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_macvtap: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan0: link becomes ready
libceph: connect [d::]:6789 error -101
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan1: link becomes ready
libceph: mon0 [d::]:6789 connect error
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_vlan: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_vlan: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_macvtap: link becomes ready
Bluetooth: hci0 command 0x0419 tx timeout
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_macvtap: link becomes ready
device veth0_vlan entered promiscuous mode
device veth0_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap0: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): vlan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vlan1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvtap0: link becomes ready
device veth1_vlan entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvlan0: link is not ready
Bluetooth: hci4 command 0x0419 tx timeout
input: syz1 as /devices/virtual/input/input6
device veth1_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macsec0: link is not ready
Bluetooth: hci3 command 0x0419 tx timeout
Bluetooth: hci1 command 0x0419 tx timeout
IPv6: ADDRCONF(NETDEV_UP): macvlan1: link is not ready
Bluetooth: hci2 command 0x0419 tx timeout
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan0: link becomes ready
Bluetooth: hci5 command 0x0419 tx timeout
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan1: link becomes ready
ceph: No mds server is up or the cluster is laggy
IPv6: ADDRCONF(NETDEV_CHANGE): macsec0: link becomes ready
IPv6: ADDRCONF(NETDEV_UP): veth0_to_batadv: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth0_macvtap: link is not ready
IPVS: ftp: loaded support on port[0] = 21
IPv6: ADDRCONF(NETDEV_UP): veth1_to_batadv: link is not ready
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
ceph: No mds server is up or the cluster is laggy
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
ceph: No mds server is up or the cluster is laggy
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
libceph: mon0 [d::]:6789 connect error
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_0: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_0
IPv6: ADDRCONF(NETDEV_UP): veth1_macvtap: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_batadv: link becomes ready
libceph: connect [d::]:6789 error -101
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_macvtap: link becomes ready
libceph: mon0 [d::]:6789 connect error
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_macvtap: link becomes ready
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_1: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_1
device veth0_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap0: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvtap0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
device veth1_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macsec0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth0_to_batadv: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_to_batadv: link is not ready
IPVS: ftp: loaded support on port[0] = 21
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_0: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_0
IPv6: ADDRCONF(NETDEV_CHANGE): macsec0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_batadv: link becomes ready
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_1: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_1
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
ceph: No mds server is up or the cluster is laggy
ptrace attach of "/root/syz-executor.5"[7984] was attempted by "/root/syz-executor.5"[9716]
ptrace attach of "/root/syz-executor.5"[7984] was attempted by "/root/syz-executor.5"[9716]
ptrace attach of "/root/syz-executor.5"[7984] was attempted by "/root/syz-executor.5"[9731]
input: syz1 as /devices/virtual/input/input7
IPVS: ftp: loaded support on port[0] = 21
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ptrace attach of "/root/syz-executor.4"[7983] was attempted by "/root/syz-executor.4"[9744]
ptrace attach of "/root/syz-executor.5"[7984] was attempted by "/root/syz-executor.5"[9749]
ptrace attach of "/root/syz-executor.0"[7980] was attempted by "/root/syz-executor.0"[9759]
libceph: connect [d::]:6789 error -101
ptrace attach of "/root/syz-executor.5"[7984] was attempted by "/root/syz-executor.5"[9761]
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ptrace attach of "/root/syz-executor.4"[7983] was attempted by "/root/syz-executor.4"[9783]
ceph: No mds server is up or the cluster is laggy
ptrace attach of "/root/syz-executor.0"[7980] was attempted by "/root/syz-executor.0"[9811]
ptrace attach of "/root/syz-executor.4"[7983] was attempted by "/root/syz-executor.4"[9812]
input: syz1 as /devices/virtual/input/input8
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
IPVS: ftp: loaded support on port[0] = 21
libceph: mon0 [d::]:6789 connect error
input: syz1 as /devices/virtual/input/input9
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
input: syz1 as /devices/virtual/input/input10
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
input: syz1 as /devices/virtual/input/input11
libceph: connect [d::]:6789 error -101
input: syz1 as /devices/virtual/input/input12
input: syz1 as /devices/virtual/input/input13
ceph: No mds server is up or the cluster is laggy
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
IPVS: ftp: loaded support on port[0] = 21
ceph: No mds server is up or the cluster is laggy
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
input: syz1 as /devices/virtual/input/input14
input: syz1 as /devices/virtual/input/input15
IPVS: ftp: loaded support on port[0] = 21
ceph: No mds server is up or the cluster is laggy
ceph: No mds server is up or the cluster is laggy
input: syz1 as /devices/virtual/input/input16
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
IPVS: ftp: loaded support on port[0] = 21
input: syz1 as /devices/virtual/input/input17
IPVS: ftp: loaded support on port[0] = 21
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
bridge0: port 3(team0) entered blocking state
libceph: mon0 [d::]:6789 connect error
bridge0: port 3(team0) entered disabled state
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
device team0 entered promiscuous mode
device team_slave_0 entered promiscuous mode
device team_slave_1 entered promiscuous mode
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered forwarding state
libceph: connect [d::]:6789 error -101
ceph: No mds server is up or the cluster is laggy
device team0 left promiscuous mode
libceph: mon0 [d::]:6789 connect error
device team_slave_0 left promiscuous mode
libceph: connect [d::]:6789 error -101
device team_slave_1 left promiscuous mode
bridge0: port 3(team0) entered disabled state
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered disabled state
IPVS: ftp: loaded support on port[0] = 21
device team0 entered promiscuous mode
device team_slave_0 entered promiscuous mode
libceph: connect [d::]:6789 error -101
device team_slave_1 entered promiscuous mode
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered forwarding state
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
device team0 left promiscuous mode
libceph: mon0 [d::]:6789 connect error
device team_slave_0 left promiscuous mode
device team_slave_1 left promiscuous mode
bridge0: port 3(team0) entered disabled state
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered disabled state
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
device team0 entered promiscuous mode
device team_slave_0 entered promiscuous mode
device team_slave_1 entered promiscuous mode
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered forwarding state
ceph: No mds server is up or the cluster is laggy
syz-executor.1 (10234) used greatest stack depth: 24920 bytes left
ceph: No mds server is up or the cluster is laggy
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'.
device team0 left promiscuous mode
device team_slave_0 left promiscuous mode
device team_slave_1 left promiscuous mode
bridge0: port 3(team0) entered disabled state
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered disabled state
device team0 entered promiscuous mode
device team_slave_0 entered promiscuous mode
device team_slave_1 entered promiscuous mode
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered forwarding state
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
cannot load conntrack support for proto=2
IPVS: ftp: loaded support on port[0] = 21
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'.
device team0 left promiscuous mode
device team_slave_0 left promiscuous mode
device team_slave_1 left promiscuous mode
bridge0: port 3(team0) entered disabled state
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'.
cannot load conntrack support for proto=2
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered disabled state
device team0 entered promiscuous mode
device team_slave_0 entered promiscuous mode
device team_slave_1 entered promiscuous mode
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered forwarding state
cannot load conntrack support for proto=2
cannot load conntrack support for proto=2
cannot load conntrack support for proto=2
cannot load conntrack support for proto=2
cannot load conntrack support for proto=2
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
cannot load conntrack support for proto=2
cannot load conntrack support for proto=2
block nbd4: Receive control failed (result -107)
block nbd4: shutting down sockets
block nbd4: Receive control failed (result -107)
block nbd4: shutting down sockets
block nbd4: Receive control failed (result -107)
block nbd4: shutting down sockets
block nbd4: Receive control failed (result -107)
block nbd4: shutting down sockets
block nbd2: Receive control failed (result -107)
block nbd2: shutting down sockets
block nbd4: Receive control failed (result -107)
block nbd2: Receive control failed (result -107)
block nbd4: shutting down sockets
block nbd2: shutting down sockets
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
block nbd4: Receive control failed (result -107)
block nbd4: shutting down sockets
block nbd0: Receive control failed (result -107)
block nbd2: Receive control failed (result -107)
block nbd0: shutting down sockets
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
block nbd2: shutting down sockets
syzbot
Aug 26, 2021, 1:13:13 PM8/26/21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: e23d55af0e1f Linux 4.19.205
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1738b06d300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ee03ce300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ee9010...@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
HEAD commit: e23d55af0e1f Linux 4.19.205
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=2221dd564152b412
dashboard link: https://syzkaller.appspot.com/bug?extid=ee9010508e9179091666
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=159313e5300000
dashboard link: https://syzkaller.appspot.com/bug?extid=ee9010508e9179091666
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ee03ce300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ee9010...@syzkaller.appspotmail.com
wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Marco Elver
Aug 31, 2021, 6:04:47 AM8/31/21
to syzkaller-lts-bugs
syzbot
Aug 31, 2021, 6:04:51 AM8/31/21
to 'Marco Elver' via syzkaller-lts-bugs, syzkaller...@googlegroups.com
> #syz invalid
I see the command but can't find the corresponding bug.
Please resend the email to syzbo...@syzkaller.appspotmail.com address
that is the sender of the bug report (also present in the Reported-by tag).
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-lts-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-lts-b...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-lts-bugs/d1d3c1ac-39b4-44c9-8857-30329746c430n%40googlegroups.com.
I see the command but can't find the corresponding bug.
Please resend the email to syzbo...@syzkaller.appspotmail.com address
that is the sender of the bug report (also present in the Reported-by tag).
> You received this message because you are subscribed to the Google Groups "syzkaller-lts-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-lts-b...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-lts-bugs/d1d3c1ac-39b4-44c9-8857-30329746c430n%40googlegroups.com.
syzbot
Aug 31, 2021, 6:10:40 AM8/31/21
to Marco Elver, el...@google.com, syzkaller...@googlegroups.com
> #syz invalid
Your 'invalid' command is accepted, but please keep syzkaller...@googlegroups.com mailing list in CC next time. It serves as a history of what happened with each bug report. Thank you.
Your 'invalid' command is accepted, but please keep syzkaller...@googlegroups.com mailing list in CC next time. It serves as a history of what happened with each bug report. Thank you.
syzbot
Aug 31, 2021, 6:13:31 AM8/31/21
to Marco Elver, el...@google.com, syzkaller...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages