All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [RFC 7/7] make accept not allocate kernel socket struct
Date: Mon, 25 Nov 2019 13:37:58 +0100	[thread overview]
Message-ID: <20191125123758.GB795@breakpoint.cc> (raw)
In-Reply-To: 8521f5a18bb86408469be4b83e7ae200a8d81e42.camel@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]

Paolo Abeni <pabeni(a)redhat.com> wrote:
> On Mon, 2019-11-25 at 03:15 +0100, Florian Westphal wrote:
> > @@ -924,10 +924,17 @@ static void mptcp_close(struct sock *sk, long timeout)
> >  
> >  	list_for_each_entry_safe(subflow, tmp, &msk->conn_list, node) {
> >  		struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
> > +		struct socket *sock = READ_ONCE(ssk->sk_socket);
> >  
> >  		pr_debug("conn_list->subflow=%p", subflow);
> >  		list_del(&subflow->node);
> > -		sock_release(ssk->sk_socket);
> > +
> > +		if (sock && sock != sk->sk_socket) {
> > +			sock_release(sock);
> 
> Double checking I read the above correctly: the condition 'sock && sock
> != sk->sk_socket' only for the first subflow of a client socket, right?
> If so, can we use the msk socket even for that one?

No, its also for outgoing connections, we use in kernel sockets for
those.

> > @@ -1443,6 +1470,20 @@ static int mptcp_stream_accept(struct socket *sock, struct socket *newsock,
> >  		return -EINVAL;
> >  
> >  	err = ssock->ops->accept(sock, newsock, flags, kern);
> > +	if (err == 0 && (newsock->sk->sk_prot == &mptcp_prot ||
> > +			 is_mptcp_v6(newsock))) {
> 
> Is not clear to me why/how we can hit the condition '!(newsock->sk-
> >sk_prot == &mptcp_prot || is_mptcp_v6(newsock))' ... Can you please
> explain?

We will hit it when we get connection from non-mptcp peer, i.e. the
!mp_capable part of mptcp_accept().

In that case sk_prot is &tcp_prot.

It might make sense to change this to
    err == 0 && newsock->sk->sk_prot != &tcp_prot

perhaps that would clarify this a bit.  WDYT?

             reply	other threads:[~2019-11-25 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 12:37 Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-25 15:31 [MPTCP] Re: [RFC 7/7] make accept not allocate kernel socket struct Florian Westphal
2019-11-25 15:06 Paolo Abeni
2019-11-25 12:24 Paolo Abeni

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=20191125123758.GB795@breakpoint.cc \
    --to=unknown@example.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.