From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v1 2/4] imptcp: cleanup fallback handling
Date: Tue, 10 Dec 2019 15:30:16 +0100 [thread overview]
Message-ID: <20191210143016.GL795@breakpoint.cc> (raw)
In-Reply-To: b6a7eee20776b33615a39b2607919e4e019b4ba6.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> On Mon, 2019-12-09 at 18:28 -0800, Mat Martineau wrote:
> > I did just say "locking looks ok", but just below this is some iteration
> > over msk->conn_list without the msk lock held. The locking there is
> > unaffected by your patch, but this might be a good chance to take a look
> > at the locking around that list iteration!
>
> Thank you for the feedback! I'll cope in the next iteration.
>
> The lockless access to msk->conn_list requires a bit more changes, I'm
> unsure I can deal with that in a timely manner. I'll try.
>
> Idea would be dropping the intermendiate inet_accept() call and open-
> code part of it, so we don't have to acquire and release the locks
> multiple times.
What about delaying
inet_sk_state_store(newsk, TCP_ESTABLISHED);
until after this unlocked list iteration?
This would/should prevent any concurrent joins and thus any
list modifications.
next reply other threads:[~2019-12-10 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 14:30 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-10 17:25 [MPTCP] Re: [PATCH v1 2/4] imptcp: cleanup fallback handling Paolo Abeni
2019-12-10 14:18 Paolo Abeni
2019-12-10 2:28 Mat Martineau
2019-12-10 2:04 Mat Martineau
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=20191210143016.GL795@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.