From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com,
syzbot+9c0268252b8ef967c62e@syzkaller.appspotmail.com,
stable@vger.kernel.org, borisp@nvidia.com,
john.fastabend@gmail.com, simon.horman@netronome.com
Subject: Re: [PATCH net] net: tls: avoid hanging tasks on the tx_lock
Date: Thu, 02 Mar 2023 04:40:18 +0000 [thread overview]
Message-ID: <167773201822.21303.9431691804610702435.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230301002857.2101894-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Feb 2023 16:28:57 -0800 you wrote:
> syzbot sent a hung task report and Eric explains that adversarial
> receiver may keep RWIN at 0 for a long time, so we are not guaranteed
> to make forward progress. Thread which took tx_lock and went to sleep
> may not release tx_lock for hours. Use interruptible sleep where
> possible and reschedule the work if it can't take the lock.
>
> Testing: existing selftest passes
>
> [...]
Here is the summary with links:
- [net] net: tls: avoid hanging tasks on the tx_lock
https://git.kernel.org/netdev/net/c/f3221361dc85
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-02 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 0:28 [PATCH net] net: tls: avoid hanging tasks on the tx_lock Jakub Kicinski
2023-03-01 9:13 ` Eric Dumazet
2023-03-02 4:40 ` patchwork-bot+netdevbpf [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=167773201822.21303.9431691804610702435.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@netronome.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+9c0268252b8ef967c62e@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).