From: syzbot <syzbot+232ebdbd36706c965ebf@syzkaller.appspotmail.com>
To: 18801353760@163.com, davem@davemloft.net, edumazet@google.com,
jhs@mojatatu.com, jiri@resnulli.us, johannes@sipsolutions.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com, yin31149@gmail.com
Subject: Re: [syzbot] memory leak in regulatory_hint_core
Date: Sat, 29 Oct 2022 22:41:15 -0700 [thread overview]
Message-ID: <0000000000007fa5c805ec39f00a@google.com> (raw)
In-Reply-To: <20221029161418.2709-1-yin31149@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFATAL: executor failed NUM times: executor NUM: exit status NUM
2022/10/30 05:33:05 SYZFATAL: executor failed 11 times: executor 0: exit status 67
SYZFAIL: wrong response packet
(errno 16: Device or resource busy)
loop exited with status 67
SYZFAIL: wrong response packet
(errno 16: Device or resource busy)
loop exited with status 67
Tested on:
commit: aae703b0 Merge tag 'for-6.1-rc1-tag' of git://git.kern..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12e3a3e2880000
kernel config: https://syzkaller.appspot.com/x/.config?x=d2f454d7d3b63980
dashboard link: https://syzkaller.appspot.com/bug?extid=232ebdbd36706c965ebf
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=10eb44b6880000
next prev parent reply other threads:[~2022-10-30 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:02 [syzbot] memory leak in regulatory_hint_core syzbot
2022-10-29 16:14 ` Hawkins Jiawei
2022-10-30 5:41 ` syzbot [this message]
2022-10-30 15:36 ` Hawkins Jiawei
2022-10-31 5:18 ` 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=0000000000007fa5c805ec39f00a@google.com \
--to=syzbot+232ebdbd36706c965ebf@syzkaller.appspotmail.com \
--cc=18801353760@163.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yin31149@gmail.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.