From: syzbot <syzbot+621fd56ba002faba6392@syzkaller.appspotmail.com>
To: agordeev@linux.ibm.com, aha310510@gmail.com,
alibuda@linux.alibaba.com, davem@davemloft.net,
edumazet@google.com, guwen@linux.alibaba.com,
jaka@linux.ibm.com, johannes.berg@intel.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
nico.escande@gmail.com, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, tonylu@linux.alibaba.com,
wenjia@linux.ibm.com
Subject: Re: [syzbot] [net?] [s390?] possible deadlock in smc_release
Date: Sat, 07 Sep 2024 09:57:04 -0700 [thread overview]
Message-ID: <000000000000d4819606218a69a2@google.com> (raw)
In-Reply-To: <00000000000031c6c50610660f17@google.com>
syzbot suspects this issue was fixed by commit:
commit b7d7f11a291830fdf69d3301075dd0fb347ced84
Author: Nicolas Escande <nico.escande@gmail.com>
Date: Tue May 28 14:26:05 2024 +0000
wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1536189f980000
start commit: 5f76499fb541 tsnep: Add link down PHY loopback support
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=bc36d99546fe9035
dashboard link: https://syzkaller.appspot.com/bug?extid=621fd56ba002faba6392
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17ad7bc3e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1461e9a7e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-09-07 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:26 [syzbot] [net?] [s390?] possible deadlock in smc_release syzbot
2024-09-07 16:57 ` syzbot [this message]
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=000000000000d4819606218a69a2@google.com \
--to=syzbot+621fd56ba002faba6392@syzkaller.appspotmail.com \
--cc=agordeev@linux.ibm.com \
--cc=aha310510@gmail.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico.escande@gmail.com \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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).