From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Shuah Khan <shuah@kernel.org>,
Simon Horman <simon.horman@netronome.com>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Paolo Pisati <paolo.pisati@canonical.com>
Subject: Re: [PATCH] selftests: net: tls: remove recv_rcvbuf test
Date: Sat, 14 Dec 2019 19:57:08 -0800 [thread overview]
Message-ID: <20191214195708.0f69a0a9@cakuba.netronome.com> (raw)
In-Reply-To: <20191213103903.29777-1-cascardo@canonical.com>
On Fri, 13 Dec 2019 07:39:02 -0300, Thadeu Lima de Souza Cascardo wrote:
> This test only works when [1] is applied, which was rejected.
>
> Basically, the errors are reported and cleared. In this particular case of
> tls sockets, following reads will block.
>
> The test case was originally submitted with the rejected patch, but, then,
> was included as part of a different patchset, possibly by mistake.
>
> [1] https://lore.kernel.org/netdev/20191007035323.4360-2-jakub.kicinski@netronome.com/#t
>
> Thanks Paolo Pisati for pointing out the original patchset where this
> appeared.
>
> Cc: Jakub Kicinski <jakub.kicinski@netronome.com>
> Fixes: 65190f77424d (selftests/tls: add a test for fragmented messages)
> Reported-by: Paolo Pisati <paolo.pisati@canonical.com>
> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Applied to net and queued for stable, thank you!
prev parent reply other threads:[~2019-12-15 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 10:39 [PATCH] selftests: net: tls: remove recv_rcvbuf test Thadeu Lima de Souza Cascardo
2019-12-13 17:52 ` Jakub Kicinski
2019-12-15 3:57 ` 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=20191214195708.0f69a0a9@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=cascardo@canonical.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paolo.pisati@canonical.com \
--cc=shuah@kernel.org \
--cc=simon.horman@netronome.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.