From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-nfs@vger.kernel.org, security@kernel.org,
Jeff Layton <jlayton@redhat.com>
Subject: Re: [PATCH] nfs4: Ensure that ACL pages sent over NFS were not allocated from the slab (v2)
Date: Fri, 04 Mar 2011 16:25:00 -0500 [thread overview]
Message-ID: <1299273900.2901.49.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1299272960-16582-1-git-send-email-nhorman@tuxdriver.com>
On Fri, 2011-03-04 at 16:09 -0500, Neil Horman wrote:
> +static int buf_to_pages_noslab(const void *buf, size_t buflen,
> + struct page **pages, unsigned int *pgbase)
> +{
> + struct page *newpage, **spages;
> + int rc = 0;
> + size_t len;
> + spages = pages;
> +
> + do {
> + len = min(PAGE_CACHE_SIZE, buflen);
> + newpage = alloc_page(GFP_KERNEL);
> +
> + if (newpage == NULL)
> + goto unwind;
> + memcpy(page_address(newpage), buf, len);
> + buf += len;
> + buflen -= len;
> + *(pages++) = newpage;
Nit: the brackets aren't needed here.
> + rc++;
> + } while (buflen != 0);
> +
> + *pgbase = 0;
> + return rc;
> +
> +unwind:
> + for(; rc > 0; rc--)
> + __free_page(spages[rc-1]);
> + return -ENOMEM;
> +}
> +
> struct nfs4_cached_acl {
> int cached;
> size_t len;
> @@ -3420,13 +3451,23 @@ static int __nfs4_proc_set_acl(struct inode *inode, const void *buf, size_t bufl
> .rpc_argp = &arg,
> .rpc_resp = &res,
> };
> - int ret;
> + int ret, i;
>
> if (!nfs4_server_supports_acls(server))
> return -EOPNOTSUPP;
> + i = buf_to_pages_noslab(buf, buflen, arg.acl_pages, &arg.acl_pgbase);
NIT: arg.acl_pgbase is already initialised to 0.
> + if (i < 0)
> + return i;
> nfs_inode_return_delegation(inode);
> - buf_to_pages(buf, buflen, arg.acl_pages, &arg.acl_pgbase);
> ret = nfs4_call_sync(server, &msg, &arg, &res, 1);
> +
> + /*
> + * Free each page after tx, so the only ref left is
> + * held by the network stack
> + */
> + for (; i > 0; i--)
> + put_page(pages[i-1]);
> +
> /*
> * Acl update can result in inode attribute update.
> * so mark the attribute cache invalid.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-03-04 21:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:44 [PATCH] nfs4: Ensure that ACL pages sent over NFS were not allocated from the slab Neil Horman
2011-03-04 16:58 ` Christoph Hellwig
2011-03-04 17:13 ` J. Bruce Fields
2011-03-04 18:45 ` Neil Horman
2011-03-04 19:33 ` J. Bruce Fields
2011-03-04 19:48 ` [Security] " Linus Torvalds
2011-03-04 20:07 ` J. Bruce Fields
2011-03-04 20:30 ` Jeff Layton
2011-03-04 20:40 ` Trond Myklebust
[not found] ` <20110304153059.79374df7-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-03-04 21:04 ` J. Bruce Fields
2011-03-04 19:01 ` Trond Myklebust
2011-03-04 19:17 ` Neil Horman
2011-03-04 19:25 ` Trond Myklebust
2011-03-04 19:59 ` Neil Horman
2011-03-04 21:09 ` [PATCH] nfs4: Ensure that ACL pages sent over NFS were not allocated from the slab (v2) Neil Horman
2011-03-04 21:25 ` Trond Myklebust [this message]
2011-03-05 0:26 ` [PATCH] nfs4: Ensure that ACL pages sent over NFS were not allocated from the slab (v3) Neil Horman
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=1299273900.2901.49.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=security@kernel.org \
/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).