From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:41942 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965180AbdEWTho (ORCPT ); Tue, 23 May 2017 15:37:44 -0400 Date: Tue, 23 May 2017 21:37:33 +0200 From: Greg KH To: "J. Bruce Fields" 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 Message-ID: <20170523193733.GA11739@kroah.com> References: <149556457717213@kroah.com> <20170523191340.GC7556@parsley.fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170523191340.GC7556@parsley.fieldses.org> Sender: stable-owner@vger.kernel.org List-ID: 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