From: David Miller <davem@davemloft.net>
To: r.hering@avm.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net/tls: Fix inverted error codes to avoid endless loop
Date: Mon, 15 Jan 2018 14:22:43 -0500 (EST) [thread overview]
Message-ID: <20180115.142243.1361498117671737724.davem@davemloft.net> (raw)
In-Reply-To: <OFDE383861.BE760332-ONC1258213.0050C28B@avm.de>
From: r.hering@avm.de
Date: Fri, 12 Jan 2018 15:42:06 +0100
> sendfile() calls can hang endless with using Kernel TLS if a socket error occurs.
> Socket error codes must be inverted by Kernel TLS before returning because
> they are stored with positive sign. If returned non-inverted they are
> interpreted as number of bytes sent, causing endless looping of the
> splice mechanic behind sendfile().
>
> Signed-off-by: Robert Hering <r.hering@avm.de>
Applied and queued up for -stable, thanks.
next prev parent reply other threads:[~2018-01-15 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 14:42 [PATCH] net/tls: Fix inverted error codes to avoid endless loop r.hering
2018-01-15 19:22 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-14 18:55 r.hering
2017-12-15 18:49 ` David Miller
2017-12-11 18:56 r.hering
2017-12-13 18:48 ` David Miller
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=20180115.142243.1361498117671737724.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=r.hering@avm.de \
/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