From: David Miller <davem@davemloft.net>
To: parameswaran.r7@gmail.com
Cc: netdev@vger.kernel.org, kleptog@svana.org, jchapman@katalix.com,
nprachan@brocade.com, rshearma@brocade.com,
stephen@networkplumber.org, sdietric@brocade.com,
ciwillia@brocade.com, lboccass@brocade.com, dfawcus@brocade.com,
bhong@brocade.com, jblunck@brocade.com, g.nault@alphalink.fr,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] l2tp: device MTU setup, tunnel socket needs a lock
Date: Mon, 17 Apr 2017 13:02:19 -0400 (EDT) [thread overview]
Message-ID: <20170417.130219.1164262427000511625.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1704121825410.1923@nelson51.eng.vyatta.net>
From: "R. Parameswaran" <parameswaran.r7@gmail.com>
Date: Wed, 12 Apr 2017 18:31:04 -0700 (PDT)
>
> The MTU overhead calculation in L2TP device set-up
> merged via commit b784e7ebfce8cfb16c6f95e14e8532d0768ab7ff
> needs to be adjusted to lock the tunnel socket while
> referencing the sub-data structures to derive the
> socket's IP overhead.
>
> Reported-by: Guillaume Nault <g.nault@alphalink.fr>
> Tested-by: Guillaume Nault <g.nault@alphalink.fr>
> Signed-off-by: R. Parameswaran <rparames@brocade.com>
Applied, thanks.
prev parent reply other threads:[~2017-04-17 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 1:31 [PATCH net-next] l2tp: device MTU setup, tunnel socket needs a lock R. Parameswaran
2017-04-17 17:02 ` David Miller [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=20170417.130219.1164262427000511625.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhong@brocade.com \
--cc=ciwillia@brocade.com \
--cc=dfawcus@brocade.com \
--cc=g.nault@alphalink.fr \
--cc=jblunck@brocade.com \
--cc=jchapman@katalix.com \
--cc=kleptog@svana.org \
--cc=lboccass@brocade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nprachan@brocade.com \
--cc=parameswaran.r7@gmail.com \
--cc=rshearma@brocade.com \
--cc=sdietric@brocade.com \
--cc=stephen@networkplumber.org \
/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