All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Schlansker <sschlansker@opentable.com>
To: Greg KH <greg@kroah.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Request backport of 'ipv6: addrconf: fix dev refcont leak when DAD failed ' to linux-4.4.y
Date: Tue, 4 Oct 2016 16:57:52 +0000	[thread overview]
Message-ID: <251C933B-27FA-4FA6-878C-A3B10103EFDB@opentable.com> (raw)
In-Reply-To: <20161004071822.GB10989@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

On Oct 4, 2016, at 12:18 AM, Greg KH <greg@kroah.com> wrote:
> 
> On Mon, Oct 03, 2016 at 07:27:35PM +0000, Steven Schlansker wrote:
>> Hi linux-stable,
>> 
>> This is a request to backport
>> 
>> 751eb6b6 ipv6: addrconf: fix dev refcont leak when DAD failed
>> https://github.com/torvalds/linux/commit/751eb6b6042a596b0080967c1a529a9fe98dac1d
>> 
>> to linux-stable 4.4.y branch.
>> It has already been applied to stable master, and 4.7.y, but not longterm 4.4.y
>> 
>> We often (1+/week) run into hosts hanging with errors like
>> 
>> [1637669.684652] unregister_netdevice: waiting for veth26dc718 to become free. Usage count = 1
>> [1637679.864366] unregister_netdevice: waiting for veth26dc718 to become free. Usage count = 1
>> 
>> and have been told that this patch likely fixes the problem.
> 
> It's already in the 4.4.22 stable release, are you not already using
> that release?
> 
> confused,

No, I am the one that is confused, I somehow managed to miss it in the history --
I think I misspelled 'refcont' as 'refcount' when searching, or something like that.

I see it now.  Thanks for pointing this out, sorry for the noise!


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      reply	other threads:[~2016-10-04 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 19:27 Request backport of 'ipv6: addrconf: fix dev refcont leak when DAD failed ' to linux-4.4.y Steven Schlansker
2016-10-04  7:18 ` Greg KH
2016-10-04 16:57   ` Steven Schlansker [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=251C933B-27FA-4FA6-878C-A3B10103EFDB@opentable.com \
    --to=sschlansker@opentable.com \
    --cc=greg@kroah.com \
    --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.