From: syzbot <syzbot+e4c27043b9315839452d@syzkaller.appspotmail.com>
To: alibuda@linux.alibaba.com, davem@davemloft.net,
dsahern@kernel.org, dust.li@linux.alibaba.com,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, schnelle@linux.ibm.com,
srikarananta01@gmail.com, syzkaller-bugs@googlegroups.com,
wenjia@linux.ibm.com
Subject: Re: [syzbot] [net?] possible deadlock in do_ip_setsockopt (4)
Date: Tue, 17 Sep 2024 15:31:02 -0700 [thread overview]
Message-ID: <00000000000093078f0622583e6e@google.com> (raw)
In-Reply-To: <aa2b8eb7-a60c-43cf-ae70-9569dd7b9e85@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file net/ipv4/ip_sockglue.c
patch: **** unexpected end of file in patch
Tested on:
commit: 2f27fce6 Merge tag 'sound-6.12-rc1' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4fc2afd52fd008bb
dashboard link: https://syzkaller.appspot.com/bug?extid=e4c27043b9315839452d
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=152784a9980000
next prev parent reply other threads:[~2024-09-17 22:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 9:50 [syzbot] [net?] possible deadlock in do_ip_setsockopt (4) syzbot
2024-08-24 16:48 ` syzbot
2024-08-25 3:37 ` syzbot
2024-09-17 21:11 ` Ananta Srikar Puranam
2024-09-17 21:28 ` syzbot
2024-09-17 21:47 ` Ananta Srikar Puranam
2024-09-17 21:58 ` Ananta Srikar Puranam
2024-09-17 22:31 ` syzbot [this message]
2024-09-17 23:50 ` [PATCH] net/ipv4: Fix circular deadlock in do_ip_setsockop AnantaSrikar
2024-09-22 9:26 ` kernel test robot
2024-09-22 16:11 ` Eric Dumazet
2024-09-22 21:04 ` Ananta Srikar Puranam
2024-09-17 22:57 ` [syzbot] [PATCH] net/ipv4: Fixing circular deadlock syzbot
2025-05-29 0:01 ` [syzbot] [net?] possible deadlock in do_ip_setsockopt (4) syzbot
[not found] <20240917225638.203403-2-srikarananta01@gmail.com>
2024-09-17 23:24 ` 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=00000000000093078f0622583e6e@google.com \
--to=syzbot+e4c27043b9315839452d@syzkaller.appspotmail.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=schnelle@linux.ibm.com \
--cc=srikarananta01@gmail.com \
--cc=syzkaller-bugs@googlegroups.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.