From: Ben Hutchings <ben@decadent.org.uk>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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 4.4-stable tree
Date: Mon, 05 Jun 2017 20:31:03 +0100 [thread overview]
Message-ID: <1496691063.3477.9.camel@decadent.org.uk> (raw)
In-Reply-To: <20170605164737.GA671@parsley.fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On Mon, 2017-06-05 at 12:47 -0400, J. Bruce Fields wrote:
> On Sat, Jun 03, 2017 at 08:55:06PM +0100, Ben Hutchings wrote:
> > You wrote:
> > > NAK.--b.
> >
> > Why, what's wrong with this? How should the bug be fixed in stable
> > branches?
>
> It was already fixed by another patch. The changelog to upstream
> 9512a16b0e12 "nfsd: Revert "nfsd: check for oversized NFSv2/v3
> arguments"" should explain the details.
>
> Apologies for the confusion.
Got it, thanks.
Ben.
--
Ben Hutchings
It is easier to write an incorrect program than to understand a correct
one.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-05 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1496424832.1989.7.camel@codethink.co.uk>
2017-06-03 19:55 ` Patch "nfsd: check for oversized NFSv2/v3 arguments" has been added to the 4.4-stable tree Ben Hutchings
2017-06-05 16:47 ` J. Bruce Fields
2017-06-05 19:31 ` Ben Hutchings [this message]
2017-05-23 18:37 gregkh
2017-05-23 19:27 ` J. Bruce Fields
-- 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=1496691063.3477.9.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=ari@synopsys.com \
--cc=bfields@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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).