From: Bryan Schumaker <bjschuma@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFSD Secinfo no name
Date: Tue, 10 May 2011 08:39:28 -0400 [thread overview]
Message-ID: <4DC93200.3070706@netapp.com> (raw)
In-Reply-To: <20110510005931.GD3600@fieldses.org>
On 05/09/2011 08:59 PM, J. Bruce Fields wrote:
> On Fri, May 06, 2011 at 02:24:39PM -0400, Bryan Schumaker wrote:
>> Hi Bruce,
>>
>> On the call yesterday you asked me to double check that secinfo no name still works in NFSD. It does still work for me.
>
> My real question was whether the bug you reported here:
>
> http://marc.info/?l=linux-nfs&m=130192462122087&w=2
>
> appears to have been fixed (in my for-2.6.40 branch) to your
> satisfaction?
Yes it has. That's what I was trying to answer, sorry if I wasn't clear.
>
> --b.
next prev parent reply other threads:[~2011-05-10 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 18:24 NFSD Secinfo no name Bryan Schumaker
2011-05-10 0:59 ` J. Bruce Fields
2011-05-10 12:39 ` Bryan Schumaker [this message]
2011-05-10 15:53 ` 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=4DC93200.3070706@netapp.com \
--to=bjschuma@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.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 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.