WARNING: can't dereference registers at 00000000000003a5 for ip retint_user+0x8/0x18 9pnet: p9_fd_create_tcp (9506): problem connecting socket to 127.0.0.1 9pnet: p9_fd_create_tcp (9518): problem connecting socket to 127.0.0.1 9pnet: p9_fd_create_tcp (9559): problem connecting socket to 127.0.0.1 Cannot find add_set index 0 as target Cannot find add_set index 0 as target Cannot find add_set index 0 as target Cannot find add_set index 0 as target syz-executor.4 (9759) used greatest stack depth: 25224 bytes left syz-executor.2 (9758) used greatest stack depth: 25176 bytes left syz-executor.1 (9763) used greatest stack depth: 25064 bytes left syz-executor.1 (9788) used greatest stack depth: 24872 bytes left audit: type=1804 audit(1608063559.832:2): pid=9887 uid=0 auid=0 ses=4 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir953453721/syzkaller.3HNTcO/19/bus" dev="sda1" ino=15809 res=1 audit: type=1804 audit(1608063559.922:3): pid=9899 uid=0 auid=0 ses=4 op="invalid_pcr" cause="ToMToU" comm="syz-executor.0" name="/root/syzkaller-testdir953453721/syzkaller.3HNTcO/19/bus" dev="sda1" ino=15809 res=1 audit: type=1804 audit(1608063559.942:4): pid=9887 uid=0 auid=0 ses=4 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir953453721/syzkaller.3HNTcO/19/bus" dev="sda1" ino=15809 res=1 audit: type=1804 audit(1608063560.162:5): pid=9917 uid=0 auid=0 ses=4 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir953453721/syzkaller.3HNTcO/20/bus" dev="sda1" ino=15781 res=1 audit: type=1804 audit(1608063560.182:6): pid=9920 uid=0 auid=0 ses=4 op="invalid_pcr" cause="open_writers" comm="syz-executor.4" name="/root/syzkaller-testdir757792805/syzkaller.TZmIsR/19/bus" dev="sda1" ino=15805 res=1 audit: type=1804 audit(1608063560.232:7): pid=9921 uid=0 auid=0 ses=4 op="invalid_pcr" cause="ToMToU" comm="syz-executor.0" name="/root/syzkaller-testdir953453721/syzkaller.3HNTcO/20/bus" dev="sda1" ino=15781 res=1 audit: type=1804 audit(1608063560.252:8): pid=9919 uid=0 auid=0 ses=4 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir332843799/syzkaller.dEeWbS/13/bus" dev="sda1" ino=15812 res=1 audit: type=1804 audit(1608063560.262:9): pid=9923 uid=0 auid=0 ses=4 op="invalid_pcr" cause="ToMToU" comm="syz-executor.4" name="/root/syzkaller-testdir757792805/syzkaller.TZmIsR/19/bus" dev="sda1" ino=15805 res=1 audit: type=1804 audit(1608063560.312:10): pid=9928 uid=0 auid=0 ses=4 op="invalid_pcr" cause="ToMToU" comm="syz-executor.1" name="/root/syzkaller-testdir332843799/syzkaller.dEeWbS/13/bus" dev="sda1" ino=15812 res=1 audit: type=1804 audit(1608063560.602:11): pid=9947 uid=0 auid=0 ses=4 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir953453721/syzkaller.3HNTcO/21/bus" dev="sda1" ino=15791 res=1 L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. device lo entered promiscuous mode Y4`Ҙ: renamed from lo device lo entered promiscuous mode Y4`Ҙ: renamed from lo