netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Chuck Lever III <chuck.lever@oracle.com>,
	Paolo Abeni <pabeni@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
	"hare@suse.com" <hare@suse.com>,
	David Howells <dhowells@redhat.com>,
	Benjamin Coddington <bcodding@redhat.com>,
	Olga Kornievskaia <kolga@netapp.com>,
	"jmeneghi@redhat.com" <jmeneghi@redhat.com>
Subject: Re: [PATCH v3 1/2] net/handshake: Create a NETLINK service for handling handshake requests
Date: Fri, 10 Feb 2023 16:06:20 +0100	[thread overview]
Message-ID: <4a4626dc-65f0-ac09-0cda-fa61d2fa48fc@suse.de> (raw)
In-Reply-To: <68DCB255-772E-4F48-BC9B-AE2F50392402@oracle.com>

On 2/10/23 15:31, Chuck Lever III wrote:
> 
> 
>> On Feb 10, 2023, at 6:41 AM, Paolo Abeni <pabeni@redhat.com> wrote:
>>
>> On Thu, 2023-02-09 at 16:34 +0000, Chuck Lever III wrote:
>>>
[ .. ]
>>> All that said, the single pending list can be replaced easily. It
>>> would be straightforward to move it into struct net, for example.
>>
>> In the end I don't see a operations needing a full list traversal.
>> handshake_nl_msg_accept walk that, but it stops at netns/proto matching
>> which should be ~always /~very soon in the typical use-case. And as you
>> said it should be easy to avoid even that.
>>
>> I think it could be useful limiting the number of pending handshake to
>> some maximum, to avoid problems in pathological/malicious scenarios.
> 
> Defending against DoS is sensible. Maybe having a per-net
> maximum of 5 or 10 pending handshakes? handshake_request() can
> return an error code if a handshake is requested while we're
> over that maximum.
> 
Can we check the source settings? Having more than one handshake in the 
queue coming from the same SRC IP/SRC Port seems a bit pointless, 
doesn't it?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		           Kernel Storage Architect
hare@suse.de			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer


  reply	other threads:[~2023-02-10 15:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 21:41 [PATCH v3 0/2] Another crack at a handshake upcall mechanism Chuck Lever
2023-02-07 21:41 ` [PATCH v3 1/2] net/handshake: Create a NETLINK service for handling handshake requests Chuck Lever
2023-02-08 16:20   ` Hannes Reinecke
2023-02-09  6:00   ` Jakub Kicinski
2023-02-09 15:43     ` Chuck Lever III
2023-02-09 16:02       ` Paolo Abeni
2023-02-09 16:34         ` Chuck Lever III
2023-02-10 11:41           ` Paolo Abeni
2023-02-10 14:31             ` Chuck Lever III
2023-02-10 15:06               ` Hannes Reinecke [this message]
2023-02-10 15:21               ` Paolo Abeni
2023-02-10 15:38                 ` Chuck Lever III
2023-02-12 15:40           ` Jamal Hadi Salim
2023-02-12 17:24             ` Chuck Lever III
2023-02-10  2:07       ` Jakub Kicinski
2023-02-10 14:17         ` Chuck Lever III
2023-02-10 18:09           ` Jakub Kicinski
2023-02-10 19:04             ` Chuck Lever III
2023-02-10 21:44               ` Jakub Kicinski
2023-02-11 20:55                 ` Chuck Lever III
2023-02-13 21:40                   ` Jakub Kicinski
2023-02-11 12:11             ` Hannes Reinecke
2023-02-13 21:55               ` Jakub Kicinski
2023-02-07 21:41 ` [PATCH v3 2/2] net/tls: Support AF_HANDSHAKE in kTLS Chuck Lever
2023-02-08 16:34   ` Hannes Reinecke
2023-02-08 17:04     ` Chuck Lever III
2023-02-08 17:48     ` Marcel Holtmann
2023-02-14  9:44 ` [PATCH v3 0/2] Another crack at a handshake upcall mechanism Hannes Reinecke
2023-02-14 11:09   ` Hannes Reinecke

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=4a4626dc-65f0-ac09-0cda-fa61d2fa48fc@suse.de \
    --to=hare@suse.de \
    --cc=bcodding@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=hare@suse.com \
    --cc=jmeneghi@redhat.com \
    --cc=kolga@netapp.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).