From: syzbot <syzbot+564b4e9875b107591b55@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: net test error: BUG: mismatching fuzzer/executor system call descriptions: ADDR vs ADDR (2)
Date: Fri, 10 Apr 2020 00:19:09 -0700 [thread overview]
Message-ID: <000000000000a3376f05a2ea8c22@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: aa81700c macsec: fix NULL dereference in macsec_upd_offloa..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=15cff49fe00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c1e98458335a7d1
dashboard link: https://syzkaller.appspot.com/bug?extid=564b4e9875b107591b55
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+564b4e9875b107591b55@syzkaller.appspotmail.com
Warning: Permanently added '10.128.1.4' (ECDSA) to the list of known hosts.
2020/04/06 18:39:32 fuzzer started
2020/04/06 18:39:33 connecting to host at 10.128.0.26:41717
2020/04/06 18:39:34 checking machine...
2020/04/06 18:39:34 checking revisions...
2020/04/06 18:39:34 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@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2020-04-10 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 7:19 syzbot [this message]
2020-04-10 7:28 ` net test error: BUG: mismatching fuzzer/executor system call descriptions: ADDR vs ADDR (2) Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000a3376f05a2ea8c22@google.com \
--to=syzbot+564b4e9875b107591b55@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.