Netdev List
 help / color / mirror / Atom feed
From: Guillaume Nault <g.nault@alphalink.fr>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [stable 4.4.y] ppp: defer netns reference release for ppp channel
Date: Mon, 9 Jan 2017 11:47:06 +0100	[thread overview]
Message-ID: <20170109104706.f4nzzl44ve7dgwhm@alphalink.fr> (raw)
In-Reply-To: <75ccacc3-a4b4-21ac-aae4-2c8968215738@simon.arlott.org.uk>

On Mon, Nov 21, 2016 at 09:12:15PM +0000, Simon Arlott wrote:
> Please apply the following patch to linux-stable 4.4.y:
> 
>   commit 205e1e255c479f3fd77446415706463b282f94e4
>   ppp: defer netns reference release for ppp channel
> 
> This is already present in 4.8.y and fixes an issue with ppp channels
> that would otherwise cause a BUG() in ppp_pernet while a global ppp
> mutex is held, preventing further ppp connections from being
> established.
> 
FYI, this is now fixed in linux-4.4.y (patch entered v4.4.40).

Regards,

Guillaume

      reply	other threads:[~2017-01-09 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 21:12 [stable 4.4.y] ppp: defer netns reference release for ppp channel Simon Arlott
2017-01-09 10:47 ` Guillaume Nault [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=20170109104706.f4nzzl44ve7dgwhm@alphalink.fr \
    --to=g.nault@alphalink.fr \
    --cc=netdev@vger.kernel.org \
    --cc=simon@fire.lp0.eu \
    /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