From: syzbot <syzbot+80cf9d55d6fd2d6a9838@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wojciech.gladysz@infogain.com
Subject: Re: [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_hash_lookup_elem
Date: Mon, 01 Jul 2024 06:27:02 -0700 [thread overview]
Message-ID: <0000000000007819d1061c2f8d46@google.com> (raw)
In-Reply-To: <20240701130014.9207-1-wojciech.gladysz@infogain.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFAIL: NL802154_CMD_SET_SHORT_ADDR failed
2024/07/01 13:26:53 ignoring optional flag "sandboxArg"="0"
2024/07/01 13:26:54 parsed 1 programs
2024/07/01 13:26:55 [FATAL] failed to run ["./syz-executor" "setup" "fault" "binfmt_misc" "usb" "802154" "swap"]: exit status 67
mkdir(/syzcgroup) failed: 17
mount(binfmt_misc) failed: 16
SYZFAIL: NL802154_CMD_SET_SHORT_ADDR failed
(errno 16: Device or resource busy)
Tested on:
commit: e478cf26 Merge branch 'bpf-fix-a-couple-of-test-failur..
git tree: https://linux.googlesource.com/linux/kernel/git/torvalds/linux
console output: https://syzkaller.appspot.com/x/log.txt?x=1780d2b9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2ad6a8768920dd4b
dashboard link: https://syzkaller.appspot.com/bug?extid=80cf9d55d6fd2d6a9838
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12b40476980000
next parent reply other threads:[~2024-07-01 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701130014.9207-1-wojciech.gladysz@infogain.com>
2024-07-01 13:27 ` syzbot [this message]
[not found] <20240701101125.13829-1-wojciech.gladysz@infogain.com>
2024-07-01 12:27 ` [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_hash_lookup_elem syzbot
2024-05-18 21:05 syzbot
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=0000000000007819d1061c2f8d46@google.com \
--to=syzbot+80cf9d55d6fd2d6a9838@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wojciech.gladysz@infogain.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.