From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.com>
Cc: <alibuda@linux.alibaba.com>, <danielyang32@g.ucla.edu>,
<danielyangkang@gmail.com>, <davem@davemloft.net>,
<edumazet@google.com>, <guwen@linux.alibaba.com>,
<hdanton@sina.com>, <jaka@linux.ibm.com>, <kuba@kernel.org>,
<kuniyu@amazon.com>, <laforge@gnumonks.org>,
<linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>,
<lkp@intel.com>, <llvm@lists.linux.dev>, <netdev@vger.kernel.org>,
<oe-kbuild-all@lists.linux.dev>,
<osmocom-net-gprs-bounces@lists.osmocom.org>,
<osmocom-net-gprs@lists.osmocom.org>, <pabeni@redhat.com>,
<pablo@netfilter.org>, <syzkaller-bugs@googlegroups.com>,
<tonylu@linux.alibaba.com>, <wenjia@linux.ibm.com>
Subject: Re: [syzbot] [net?] possible deadlock in gtp_encap_enable_socket
Date: Mon, 12 May 2025 15:10:26 -0700 [thread overview]
Message-ID: <20250512221029.56357-1-kuniyu@amazon.com> (raw)
In-Reply-To: <68221ce4.050a0220.f2294.0070.GAE@google.com>
From: syzbot <syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.com>
Date: Mon, 12 May 2025 09:08:04 -0700
> 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=140462f4580000
> start commit: 9410645520e9 Merge tag 'net-next-6.12' of git://git.kernel..
> git tree: net-next
> kernel config: https://syzkaller.appspot.com/x/.config?x=37c006d80708398d
> dashboard link: https://syzkaller.appspot.com/bug?extid=e953a8f3071f5c0a28fd
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16215ca9980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110c6c27980000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: smc: Fix lockdep false-positive for IPPROTO_SMC.
#syz fix: smc: Fix lockdep false-positive for IPPROTO_SMC.
next prev parent reply other threads:[~2025-05-12 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 15:46 [syzbot] [net?] possible deadlock in gtp_encap_enable_socket syzbot
2024-10-01 0:57 ` [syzbot] test syzbot
2024-10-05 2:39 ` [syzbot] patch test syzbot
2024-10-05 9:28 ` [syzbot] [net?] possible deadlock in gtp_encap_enable_socket Hillf Danton
2024-10-05 9:57 ` syzbot
2024-10-30 12:02 ` Pablo Neira Ayuso
2025-05-12 16:08 ` syzbot
2025-05-12 22:10 ` Kuniyuki Iwashima [this message]
[not found] <CAGiJo8TzPyoxUoTV=48uowQPPywbCZ6X1fRRF5KGYFJyhkY5_A@mail.gmail.com>
2024-10-01 1:20 ` syzbot
[not found] <CAGiJo8QbFa1ygs7e3T8uZbvRb+e-+Eu8UBef1k6ZLkr5eJ3x1Q@mail.gmail.com>
2024-10-05 3:36 ` 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=20250512221029.56357-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=alibuda@linux.alibaba.com \
--cc=danielyang32@g.ucla.edu \
--cc=danielyangkang@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=hdanton@sina.com \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=osmocom-net-gprs-bounces@lists.osmocom.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.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