From: Jeffrey E Altman <jaltman@auristor.com>
To: YueHaibing <yuehaibing@huawei.com>, dhowells@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-afs@lists.infradead.org
Subject: Re: [PATCH -next] afs: use correct afs_call_type in yfs_fs_store_opaque_acl2
Date: Fri, 9 Aug 2019 13:34:42 -0400 [thread overview]
Message-ID: <b008a1eb-6665-8dde-2aa4-e71dddaafd42@auristor.com> (raw)
In-Reply-To: <20190809084323.46204-1-yuehaibing@huawei.com>
[-- Attachment #1.1: Type: text/plain, Size: 962 bytes --]
This change is correct.
On 8/9/2019 4:43 AM, YueHaibing wrote:
> It seems that 'yfs_RXYFSStoreOpaqueACL2' should be use in
> yfs_fs_store_opaque_acl2().
>
> Fixes: f5e4546347bc ("afs: Implement YFS ACL setting")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> fs/afs/yfsclient.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/afs/yfsclient.c b/fs/afs/yfsclient.c
> index 2575503..ca24528 100644
> --- a/fs/afs/yfsclient.c
> +++ b/fs/afs/yfsclient.c
> @@ -2171,7 +2171,7 @@ int yfs_fs_store_opaque_acl2(struct afs_fs_cursor *fc, const struct afs_acl *acl
> key_serial(fc->key), vnode->fid.vid, vnode->fid.vnode);
>
> size = round_up(acl->size, 4);
> - call = afs_alloc_flat_call(net, &yfs_RXYFSStoreStatus,
> + call = afs_alloc_flat_call(net, &yfs_RXYFSStoreOpaqueACL2,
> sizeof(__be32) * 2 +
> sizeof(struct yfs_xdr_YFSFid) +
> sizeof(__be32) + size,
>
[-- Attachment #1.2: jaltman.vcf --]
[-- Type: text/x-vcard, Size: 283 bytes --]
begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:AuriStor, Inc.
adr:;;255 W 94TH ST STE 6B;New York;NY;10025-6985;United States
email;internet:jaltman@auristor.com
title:CEO
tel;work:+1-212-769-9018
url:https://www.linkedin.com/in/jeffreyaltman/
version:2.1
end:vcard
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4033 bytes --]
prev parent reply other threads:[~2019-08-09 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 8:43 YueHaibing
2019-08-09 17:34 ` Jeffrey E Altman [this message]
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=b008a1eb-6665-8dde-2aa4-e71dddaafd42@auristor.com \
--to=jaltman@auristor.com \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@huawei.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
Powered by JetHome