From: syzbot <syzbot+bef85a6996d1737c1a2f@syzkaller.appspotmail.com>
To: agordeev@linux.ibm.com, alibuda@linux.alibaba.com,
davem@davemloft.net, edumazet@google.com,
guwen@linux.alibaba.com, horms@kernel.org, jaka@linux.ibm.com,
kuba@kernel.org, kuniyu@amazon.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
tonylu@linux.alibaba.com, wenjia@linux.ibm.com
Subject: Re: [syzbot] [smc?] possible deadlock in smc_switch_to_fallback (2)
Date: Sat, 31 May 2025 09:20:01 -0700 [thread overview]
Message-ID: <683b2c31.a00a0220.d8eae.001b.GAE@google.com> (raw)
In-Reply-To: <000000000000ec1f6b061ba43f7d@google.com>
syzbot suspects this issue was fixed by commit:
commit 752e2217d789be2c6a6ac66554b981cd71cd9f31
Author: Kuniyuki Iwashima <kuniyu@amazon.com>
Date: Mon Apr 7 17:03:17 2025 +0000
smc: Fix lockdep false-positive for IPPROTO_SMC.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13833ed4580000
start commit: 47e55e4b410f openvswitch: fix lockup on tx to unregisterin..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=4ef22c4fce5135b4
dashboard link: https://syzkaller.appspot.com/bug?extid=bef85a6996d1737c1a2f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14832cb0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e17218580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: smc: Fix lockdep false-positive for IPPROTO_SMC.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-05-31 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 15:15 [syzbot] [net?] [s390?] possible deadlock in smc_switch_to_fallback (2) syzbot
2024-07-27 17:46 ` syzbot
2025-05-31 16:20 ` syzbot [this message]
2025-07-04 14:26 ` Tetsuo Handa
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=683b2c31.a00a0220.d8eae.001b.GAE@google.com \
--to=syzbot+bef85a6996d1737c1a2f@syzkaller.appspotmail.com \
--cc=agordeev@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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.