lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 17 Apr 2017 13:02:19 -0400 (EDT) From: David Miller <davem@...emloft.net> To: parameswaran.r7@...il.com Cc: netdev@...r.kernel.org, kleptog@...na.org, jchapman@...alix.com, nprachan@...cade.com, rshearma@...cade.com, stephen@...workplumber.org, sdietric@...cade.com, ciwillia@...cade.com, lboccass@...cade.com, dfawcus@...cade.com, bhong@...cade.com, jblunck@...cade.com, g.nault@...halink.fr, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next] l2tp: device MTU setup, tunnel socket needs a lock From: "R. Parameswaran" <parameswaran.r7@...il.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@...halink.fr> > Tested-by: Guillaume Nault <g.nault@...halink.fr> > Signed-off-by: R. Parameswaran <rparames@...cade.com> Applied, thanks.
Powered by blists - more mailing lists