All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: syzbot <syzbot+9c0268252b8ef967c62e@syzkaller.appspotmail.com>,
	borisp@nvidia.com, bpf@vger.kernel.org, davem@davemloft.net,
	john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] INFO: task hung in tls_sw_sendpage (3)
Date: Tue, 28 Feb 2023 14:51:32 -0800	[thread overview]
Message-ID: <20230228145132.6d09453f@kernel.org> (raw)
In-Reply-To: <CANn89i+ooMT_G9aL8keZ-WOcAKqpC44OLQNGvfUtjA6PW-yxcA@mail.gmail.com>

On Tue, 28 Feb 2023 12:23:46 +0100 Eric Dumazet wrote:
> This report mentions sendpage, but sendmsg() would have the same issue.
> 
> A thread might be blocked in sk_stream_wait_memory() with the mutex
> held, for an arbitrary amount of time,
> say if the remote peer stays in RWIN 0 for hours.
> 
> This prevents tx_work from making progress, and
> tls_sw_cancel_work_tx() would be stuck forever.
> 
> The consensus is that the kernel shouts a warning if a thread has been
> waiting on a mutex
> more than 120 seconds (check_hung_uninterruptible_tasks())

Thanks for explaining, let's see if I can hack a fix together..

      reply	other threads:[~2023-02-28 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 20:33 [syzbot] [net?] INFO: task hung in tls_sw_sendpage (3) syzbot
2023-02-27 20:35 ` Eric Dumazet
2023-02-27 23:53   ` Jakub Kicinski
2023-02-28 11:23     ` Eric Dumazet
2023-02-28 22:51       ` Jakub Kicinski [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=20230228145132.6d09453f@kernel.org \
    --to=kuba@kernel.org \
    --cc=borisp@nvidia.com \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+9c0268252b8ef967c62e@syzkaller.appspotmail.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 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.