Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1622167
| From | David Miller <davem@davemloft.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH net-next v1 1/1] L2TP device MTU setup - tunnel socket needs a lock |
| Date | 2017-04-12 16:20 +0200 |
| Message-ID | <tvrhM-5ul-1@gated-at.bofh.it> (permalink) |
| References | <tvgZ3-7E0-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
From: "R. Parameswaran" <parameswaran.r7@gmail.com> Date: Tue, 11 Apr 2017 20:14:37 -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. This is missing a proper signoff. The subject line also needs to be fixed "[PATCH net-next] l2tp: " as explained by Guillaume. Thanks.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH net-next v1 1/1] L2TP device MTU setup - tunnel socket needs a lock "R. Parameswaran" <parameswaran.r7@gmail.com> - 2017-04-12 05:20 +0200
Re: [PATCH net-next v1 1/1] L2TP device MTU setup - tunnel socket needs a lock Guillaume Nault <g.nault@alphalink.fr> - 2017-04-12 10:00 +0200
Re: [PATCH net-next v1 1/1] L2TP device MTU setup - tunnel socket needs a lock R Parameswaran <parameswaran.r7@gmail.com> - 2017-04-12 22:50 +0200
Re: [PATCH net-next v1 1/1] L2TP device MTU setup - tunnel socket needs a lock David Miller <davem@davemloft.net> - 2017-04-12 16:20 +0200
Re: [PATCH net-next v1 1/1] L2TP device MTU setup - tunnel socket needs a lock R Parameswaran <parameswaran.r7@gmail.com> - 2017-04-12 22:40 +0200
csiph-web