From: syzbot <syzbot+5efae91f60932839f0a5@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
fmancera@suse.de, horms@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] possible deadlock in inet6_getname
Date: Mon, 16 Feb 2026 03:45:02 -0800 [thread overview]
Message-ID: <6993033e.a70a0220.2c38d7.00eb.GAE@google.com> (raw)
In-Reply-To: <ae86f151-0480-45f2-870e-7378e1607058@suse.de>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file net/rds/tcp_listen.c
Hunk #1 FAILED at 59.
1 out of 1 hunk FAILED
Tested on:
commit: 37a93dd5 Merge tag 'net-next-7.0' of git://git.kernel...
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=2c36acc86fd56a9d
dashboard link: https://syzkaller.appspot.com/bug?extid=5efae91f60932839f0a5
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=14aef15a580000
prev parent reply other threads:[~2026-02-16 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 12:15 [syzbot] [net?] possible deadlock in inet6_getname syzbot
2026-02-13 17:26 ` Eric Dumazet
2026-02-13 18:51 ` Gerd Rausch
2026-02-14 18:25 ` Fernando Fernandez Mancera
2026-02-17 16:59 ` Gerd Rausch
2026-02-17 17:03 ` Fernando Fernandez Mancera
2026-02-17 17:13 ` Gerd Rausch
2026-02-17 17:19 ` Fernando Fernandez Mancera
2026-02-17 17:28 ` Gerd Rausch
2026-02-17 18:58 ` Gerd Rausch
2026-02-17 20:26 ` Fernando Fernandez Mancera
2026-02-17 21:57 ` Allison Henderson
2026-02-16 11:32 ` Fernando Fernandez Mancera
2026-02-16 11:45 ` 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=6993033e.a70a0220.2c38d7.00eb.GAE@google.com \
--to=syzbot+5efae91f60932839f0a5@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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