From: syzbot <syzbot+ac648b0525be1feba506@syzkaller.appspotmail.com>
To: casey@schaufler-ca.com, davem@davemloft.net, edumazet@google.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, paul@paul-moore.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in ieee80211_free_ack_frame (2)
Date: Thu, 13 Jul 2023 10:49:31 -0700 [thread overview]
Message-ID: <0000000000005ac8fc060061f4c5@google.com> (raw)
In-Reply-To: <000000000000c2dccb05d0cee49a@google.com>
syzbot suspects this issue was fixed by commit:
commit 1661372c912d1966e21e0cb5463559984df8249b
Author: Paul Moore <paul@paul-moore.com>
Date: Tue Feb 7 22:06:51 2023 +0000
lsm: move the program execution hook comments to security/security.c
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1024a074a80000
start commit: 33189f0a94b9 r8169: fix RTL8168H and RTL8107E rx crc error
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=ea09b0836073ee4
dashboard link: https://syzkaller.appspot.com/bug?extid=ac648b0525be1feba506
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15346b1ec80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=162e3b89c80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: lsm: move the program execution hook comments to security/security.c
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-13 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 7:38 [syzbot] WARNING in ieee80211_free_ack_frame (2) syzbot
2023-03-26 8:21 ` [syzbot] [wireless?] " syzbot
2023-07-13 17:49 ` syzbot [this message]
2023-07-13 19:00 ` Aleksandr Nogikh
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=0000000000005ac8fc060061f4c5@google.com \
--to=syzbot+ac648b0525be1feba506@syzkaller.appspotmail.com \
--cc=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=paul@paul-moore.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).