linux-kernel - linux-next test error: BUG: mismatching fuzzer/executor system call descriptions: ADDR vs ADDR (3)

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]

Date:   Fri, 10 Apr 2020 00:29:15 -0700
From:   syzbot <syzbot+528253fcf7f3c9d2747a@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: linux-next test error: BUG: mismatching fuzzer/executor system call
 descriptions: ADDR vs ADDR (3)

Hello,

syzbot found the following crash on:

HEAD commit:    b2e2a818 Add linux-next specific files for 20200406
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12ff05fbe00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=595413e7170f444b
dashboard link: https://syzkaller.appspot.com/bug?extid=528253fcf7f3c9d2747a
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

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

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+528253fcf7f3c9d2747a@...kaller.appspotmail.com

Warning: Permanently added '10.128.1.24' (ECDSA) to the list of known hosts.
2020/04/06 07:22:58 fuzzer started
2020/04/06 07:22:59 connecting to host at 10.128.0.26:46701
2020/04/06 07:22:59 checking machine...
2020/04/06 07:22:59 checking revisions...
2020/04/06 07:22:59 BUG: mismatching fuzzer/executor system call descriptions: 670a1e865c0bc7d60e9886acf4666ee3677e346e vs f787d115f9efa49fdd59261850f5c05f43fbe327
syzkaller login: 


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.