From: Greg KH <greg@kroah.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: stable@vger.kernel.org, ben@decadent.org.uk, david@sinquin.eu,
hch@infradead.org, viro@zeniv.linux.org.uk, agruenba@redhat.com
Subject: Re: [PATCH 2/2] nfsd: check permissions when setting ACLs
Date: Wed, 13 Jul 2016 09:26:29 +0900 [thread overview]
Message-ID: <20160713002629.GA17021@kroah.com> (raw)
In-Reply-To: <1468355289-4014-2-git-send-email-bfields@redhat.com>
On Tue, Jul 12, 2016 at 04:28:09PM -0400, J. Bruce Fields wrote:
> From: Ben Hutchings <ben@decadent.org.uk>
>
> commit ec11e9872f0f23dcd6b7c2ebcaed116bc3b9659b upstream.
I think you mean 999653786df6954a31044528ac3f7a5dadca08f4 :)
Thanks for both of these, now queued up.
greg k-h
next prev parent reply other threads:[~2016-07-13 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 20:28 [PATCH 1/2] posix_acl: Add set_posix_acl J. Bruce Fields
2016-07-12 20:28 ` [PATCH 2/2] nfsd: check permissions when setting ACLs J. Bruce Fields
2016-07-13 0:26 ` Greg KH [this message]
2016-07-13 1:20 ` J. Bruce Fields
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=20160713002629.GA17021@kroah.com \
--to=greg@kroah.com \
--cc=agruenba@redhat.com \
--cc=ben@decadent.org.uk \
--cc=bfields@redhat.com \
--cc=david@sinquin.eu \
--cc=hch@infradead.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).