From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Guillaume Nault <g.nault@alphalink.fr>,
"David S . Miller" <davem@davemloft.net>,
Stable <stable@vger.kernel.org>
Subject: Re: [PATCH for-4.9 0/5] l2tp session lookup fixes
Date: Mon, 3 Jul 2017 10:48:11 +0200 [thread overview]
Message-ID: <20170703084811.GD11757@kroah.com> (raw)
In-Reply-To: <1498492039-26905-1-git-send-email-amit.pundir@linaro.org>
On Mon, Jun 26, 2017 at 09:17:14PM +0530, Amit Pundir wrote:
> Hi,
>
> Kindly consider/review following l2tp fixes for stable 4.9.y.
>
> This patchset fix race in l2tp sessions, avoid duplicate sessions
> and probable "use after free" bugs. Here is the original submission
> https://www.mail-archive.com/netdev@vger.kernel.org/msg161040.html
>
> Cherry-picked and build tested on Linux 4.9.34 for
> ARCH=x86/x86_64 + allmodconfig.
Thanks for these, should they also go into 4.4 and older kernels? If
so, care to make up patches for them?
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-03 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 15:47 [PATCH for-4.9 0/5] l2tp session lookup fixes Amit Pundir
2017-06-26 15:47 ` [PATCH for-4.9 1/5] l2tp: fix race in l2tp_recv_common() Amit Pundir
2017-06-26 15:47 ` [PATCH for-4.9 2/5] l2tp: ensure session can't get removed during pppol2tp_session_ioctl() Amit Pundir
2017-06-26 15:47 ` [PATCH for-4.9 3/5] l2tp: fix duplicate session creation Amit Pundir
2017-06-26 15:47 ` [PATCH for-4.9 4/5] l2tp: hold session while sending creation notifications Amit Pundir
2017-06-26 15:47 ` [PATCH for-4.9 5/5] l2tp: take a reference on sessions used in genetlink handlers Amit Pundir
2017-06-27 7:57 ` [PATCH for-4.9 0/5] l2tp session lookup fixes Guillaume Nault
2017-07-03 8:48 ` Greg KH [this message]
2017-07-03 8:56 ` Amit Pundir
2017-07-03 9:03 ` Greg KH
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=20170703084811.GD11757@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--cc=davem@davemloft.net \
--cc=g.nault@alphalink.fr \
--cc=stable@vger.kernel.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 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.