From: Suresh Jayaraman <sjayaraman@suse.de>
To: hooanon05-/E1597aS9LR3+QwDJ9on6Q@public.gmane.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
jamagallon-sh/6fXdz2Rs@public.gmane.org,
LKML <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com,
lists@fuchsschwanzdomain.de
Subject: Re: Problems with default ACLs over NFS
Date: Mon, 20 Apr 2009 11:05:58 +0530 [thread overview]
Message-ID: <49EC09BE.6090508@suse.de> (raw)
In-Reply-To: <7064.1240204656@jrobl>
hooanon05-/E1597aS9LR3+QwDJ9on6Q@public.gmane.org wrote:
> Suresh Jayaraman:
>> The following patch from Trond should fix this issue, I think.
>>
>>
>> From: Trond Myklebust <Trond.Myklebust@netapp.com>
>> Date: Wed, 15 Apr 2009 13:58:45 -0400
>> Subject: [PATCH] NFS: Fix the XDR iovec calculation in nfs3_xdr_setaclargs
>>
>> Commit ae46141ff08f1965b17c531b571953c39ce8b9e2 (NFSv3: Fix posix ACL code)
>> introduces a bug in the calculation of the XDR header iovec. In the case
>> where we are inlining the acls, we need to adjust the length of the iovec
>> req->rq_svec, in addition to adjusting the total buffer length.
>
> Thanx.
> But which tree is this patch applied?
>
Not yet applied. I guess it's queued up in Trond's git.
Thanks,
--
Suresh Jayaraman
WARNING: multiple messages have this Message-ID (diff)
From: Suresh Jayaraman <sjayaraman@suse.de>
To: hooanon05@yahoo.co.jp
Cc: Andrew Morton <akpm@linux-foundation.org>,
jamagallon@ono.com, LKML <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com,
lists@fuchsschwanzdomain.de
Subject: Re: Problems with default ACLs over NFS
Date: Mon, 20 Apr 2009 11:05:58 +0530 [thread overview]
Message-ID: <49EC09BE.6090508@suse.de> (raw)
In-Reply-To: <7064.1240204656@jrobl>
hooanon05@yahoo.co.jp wrote:
> Suresh Jayaraman:
>> The following patch from Trond should fix this issue, I think.
>>
>>
>> From: Trond Myklebust <Trond.Myklebust@netapp.com>
>> Date: Wed, 15 Apr 2009 13:58:45 -0400
>> Subject: [PATCH] NFS: Fix the XDR iovec calculation in nfs3_xdr_setaclargs
>>
>> Commit ae46141ff08f1965b17c531b571953c39ce8b9e2 (NFSv3: Fix posix ACL code)
>> introduces a bug in the calculation of the XDR header iovec. In the case
>> where we are inlining the acls, we need to adjust the length of the iovec
>> req->rq_svec, in addition to adjusting the total buffer length.
>
> Thanx.
> But which tree is this patch applied?
>
Not yet applied. I guess it's queued up in Trond's git.
Thanks,
--
Suresh Jayaraman
next prev parent reply other threads:[~2009-04-20 5:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 21:24 Problems with default ACLs over NFS J.A. Magallón
[not found] ` <20090323222427.00bb24e7-BIo4oXGMtDgJmsy6czSMtA@public.gmane.org>
2009-03-27 0:05 ` Andrew Morton
2009-03-27 0:05 ` Andrew Morton
2009-03-27 22:50 ` hooanon05
2009-04-20 4:42 ` Suresh Jayaraman
2009-04-20 4:42 ` Suresh Jayaraman
2009-04-20 5:17 ` hooanon05
2009-04-20 5:35 ` Suresh Jayaraman [this message]
2009-04-20 5:35 ` Suresh Jayaraman
2009-04-20 14:18 ` Sven Geggus
2009-04-21 5:00 ` Suresh Jayaraman
-- strict thread matches above, loose matches on Subject: below --
2009-04-19 15:03 Sven Geggus
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=49EC09BE.6090508@suse.de \
--to=sjayaraman@suse.de \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=hooanon05-/E1597aS9LR3+QwDJ9on6Q@public.gmane.org \
--cc=jamagallon-sh/6fXdz2Rs@public.gmane.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lists@fuchsschwanzdomain.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.