From: syzbot <syzbot+160a7250e255d25725eb@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
kuba@kernel.org, kvalo@kernel.org, linux-afs@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, pchelkin@ispras.ru, quic_kvalo@quicinc.com,
syzkaller-bugs@googlegroups.com, toke@toke.dk
Subject: Re: [syzbot] [afs?] general protection fault in skb_queue_tail (3)
Date: Sat, 15 Jul 2023 00:22:18 -0700 [thread overview]
Message-ID: <000000000000ea91fa0600816cb8@google.com> (raw)
In-Reply-To: <0000000000000de35905ead6dcc1@google.com>
syzbot suspects this issue was fixed by commit:
commit 061b0cb9327b80d7a0f63a33e7c3e2a91a71f142
Author: Fedor Pchelkin <pchelkin@ispras.ru>
Date: Wed May 17 15:03:17 2023 +0000
wifi: ath9k: don't allow to overwrite ENDPOINT0 attributes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12253b7ca80000
start commit: 98555239e4c3 Merge tag 'arc-6.1-fixes' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=701f2aae1cb0470e
dashboard link: https://syzkaller.appspot.com/bug?extid=160a7250e255d25725eb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1482f0b6880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119e4dce880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: wifi: ath9k: don't allow to overwrite ENDPOINT0 attributes
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-15 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 14:03 [syzbot] general protection fault in skb_queue_tail (3) syzbot
2023-07-15 7:22 ` syzbot [this message]
2023-07-20 13:22 ` [syzbot] [afs?] " Fedor Pchelkin
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=000000000000ea91fa0600816cb8@google.com \
--to=syzbot+160a7250e255d25725eb@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pchelkin@ispras.ru \
--cc=quic_kvalo@quicinc.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=toke@toke.dk \
/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.