From: Ananta Srikar Puranam <srikarananta01@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: syzbot+e4c27043b9315839452d@syzkaller.appspotmail.com,
alibuda@linux.alibaba.com, davem@davemloft.net,
dsahern@kernel.org, dust.li@linux.alibaba.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, schnelle@linux.ibm.com,
syzkaller-bugs@googlegroups.com, wenjia@linux.ibm.com
Subject: Re: [PATCH] net/ipv4: Fix circular deadlock in do_ip_setsockop
Date: Sun, 22 Sep 2024 17:04:22 -0400 [thread overview]
Message-ID: <ef4422fd-f4aa-44dd-b1ff-350761db59d5@gmail.com> (raw)
In-Reply-To: <CANn89iLxa6V7BZSzmj5A979M2ZObj-CcDD_izeKqtRCZj-+pmQ@mail.gmail.com>
On 22/09/24 12:11 pm, Eric Dumazet wrote:
> I think you missed an earlier conversation about SMC being at fault here.
You're right, I missed the earlier discussion about SMC. I apologize for
the oversight and thank you for pointing it out. As a first-time
contributor, I'll be more diligent in researching existing discussions
before submitting patches in the future.
Best regards,
Srikar
next prev parent reply other threads:[~2024-09-22 21:04 UTC|newest]
Thread overview: 14+ 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
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 [this message]
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
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=ef4422fd-f4aa-44dd-b1ff-350761db59d5@gmail.com \
--to=srikarananta01@gmail.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=syzbot+e4c27043b9315839452d@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®