stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: ari@synopsys.com, thaan@synopsys.com, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "nfsd: check for oversized NFSv2/v3 arguments" has been added to the 3.18-stable tree
Date: Tue, 23 May 2017 21:37:33 +0200	[thread overview]
Message-ID: <20170523193733.GA11739@kroah.com> (raw)
In-Reply-To: <20170523191340.GC7556@parsley.fieldses.org>

On Tue, May 23, 2017 at 03:13:41PM -0400, J. Bruce Fields wrote:
> NAK to this and all other backports of 51f567777799 (but I'll try to NAK
> them all individually).
> 
> I also tentatively have a stable cc on the upstream revert that I've got
> queued up--I figured that might be good just in case any backports slip
> through.  (But if getting the cc on a revert that probably doesn't apply
> is more annoying, tell me.)
> 
> Apologies for this one, the problem was fixed by e6838a29ecb "nfsd:
> check for oversized NFSv2/v3 arguments", but I accidentally left this
> earlier attempt at a fix on the branch that I submitted for 4.12.

Thanks for letting me know, I've now dropped this from all of the stable
queues.

greg k-h

  reply	other threads:[~2017-05-23 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 18:36 Patch "nfsd: check for oversized NFSv2/v3 arguments" has been added to the 3.18-stable tree gregkh
2017-05-23 19:13 ` J. Bruce Fields
2017-05-23 19:37   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-30 14:11 gregkh

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=20170523193733.GA11739@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ari@synopsys.com \
    --cc=bfields@redhat.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=thaan@synopsys.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).