From: Greg KH <greg@kroah.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: stable@vger.kernel.org, Kinglong Mee <kinglongmee@gmail.com>,
Anna Schumaker <Anna.Schumaker@Netapp.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Stable request to fix a reference leak and list corruption
Date: Sun, 2 Jul 2017 10:53:54 +0200 [thread overview]
Message-ID: <20170702085354.GA20685@kroah.com> (raw)
In-Reply-To: <20170628144758.12225-1-trond.myklebust@primarydata.com>
On Wed, Jun 28, 2017 at 10:47:57AM -0400, Trond Myklebust wrote:
> Hi Greg,
>
> Could we please queue up the following patch as a stable fix for
> commit a974deee47? It needs to be applied to v4.10 and older.
Now applied, thanks.
greg k-h
next prev parent reply other threads:[~2017-07-02 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 14:47 [PATCH] Stable request to fix a reference leak and list corruption Trond Myklebust
2017-06-28 14:47 ` [PATCH] NFSv4: fix a reference leak caused WARNING messages Trond Myklebust
2017-07-02 8:53 ` Greg KH [this message]
2017-07-05 20:29 ` [PATCH] Stable request to fix a reference leak and list corruption Robert Kudyba
2017-07-05 20:59 ` Trond Myklebust
2017-07-06 14:24 ` Robert Kudyba
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=20170702085354.GA20685@kroah.com \
--to=greg@kroah.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=kinglongmee@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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;
as well as URLs for NNTP newsgroup(s).