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: Sat, 03 Jun 2017 20:55:06 +0100 [thread overview]
Message-ID: <1496519706.3992.40.camel@decadent.org.uk> (raw)
In-Reply-To: <1496424832.1989.7.camel@codethink.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
You wrote:
> NAK.--b.
Why, what's wrong with this? How should the bug be fixed in stable
branches?
Ben.
> On Tue, May 23, 2017 at 08:37:32PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > nfsd: check for oversized NFSv2/v3 arguments
> >
> > to the 4.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > nfsd-check-for-oversized-nfsv2-v3-arguments.patch
> > and it can be found in the queue-4.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From 51f567777799c9d85a778302b9eb61cf15214a98 Mon Sep 17 00:00:00 2001
> > From: "J. Bruce Fields" <bfields@redhat.com>
> > Date: Thu, 6 Apr 2017 22:36:31 -0400
> > Subject: nfsd: check for oversized NFSv2/v3 arguments
> > MIME-Version: 1.0
> > Content-Type: text/plain; charset=UTF-8
> > Content-Transfer-Encoding: 8bit
> >
> > From: J. Bruce Fields <bfields@redhat.com>
> >
> > commit 51f567777799c9d85a778302b9eb61cf15214a98 upstream.
[...]
--
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2017-06-03 19:55 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 ` Ben Hutchings [this message]
2017-06-05 16:47 ` Patch "nfsd: check for oversized NFSv2/v3 arguments" has been added to the 4.4-stable tree J. Bruce Fields
2017-06-05 19:31 ` Ben Hutchings
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=1496519706.3992.40.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).