From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Schumaker, Bryan" <Bryan.Schumaker@netapp.com>
Subject: RE: 3.7-rc1 NFSv3/sec=krb5 mkdir failure
Date: Wed, 24 Oct 2012 20:07:55 +0000 [thread overview]
Message-ID: <4FA345DA4F4AE44899BD2B03EEEC2FA9092906F7@SACEXCMBX04-PRD.hq.netapp.com> (raw)
In-Reply-To: <20121024200249.GC6697@fieldses.org>
> -----Original Message-----
> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-
> owner@vger.kernel.org] On Behalf Of J. Bruce Fields
> Sent: Wednesday, October 24, 2012 4:03 PM
> To: linux-nfs@vger.kernel.org; Myklebust, Trond; Schumaker, Bryan
> Subject: Re: 3.7-rc1 NFSv3/sec=krb5 mkdir failure
>
> Anyone get a chance to look at this? It seems very reproduceable.
>
> --b.
>
> On Tue, Oct 16, 2012 at 08:58:32AM -0400, bfields wrote:
> > On 3.7-rc1:
> >
> > client# mount -tnfs -osec=krb5,vers=3 server:/exports/ext4 /mnt/
> >
> > server# ls -l /exports/ext4|grep TMP
> > server#
> >
> > # mkdir /mnt/TMP
> > mkdir: cannot create directory `/mnt/TMP': Permission denied
> >
> > server# ls -l /exports/ext4|grep TMP
> > drwxr-xr-x 2 nfsnobody nfsnobody 4096 Oct 16 08:56 TMP
> > server#
> >
> > Wireshark also shows that the create succeeds.
Can you share the wireshark trace?
Cheers
Trond
next prev parent reply other threads:[~2012-10-24 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 12:58 3.7-rc1 NFSv3/sec=krb5 mkdir failure J. Bruce Fields
2012-10-24 20:02 ` J. Bruce Fields
2012-10-24 20:07 ` Myklebust, Trond [this message]
2012-10-24 20:15 ` J. Bruce Fields
2012-10-24 20:31 ` Myklebust, Trond
2012-10-24 20:38 ` J. Bruce Fields
2012-10-24 20:34 ` Myklebust, Trond
2012-10-24 20:40 ` J. Bruce Fields
2012-10-28 16:15 ` J. Bruce Fields
2012-11-16 2:03 ` Chuck Lever
2012-11-16 2:24 ` J. Bruce Fields
2012-11-16 2:26 ` Myklebust, Trond
2012-11-16 2:41 ` Chuck Lever
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=4FA345DA4F4AE44899BD2B03EEEC2FA9092906F7@SACEXCMBX04-PRD.hq.netapp.com \
--to=trond.myklebust@netapp.com \
--cc=Bryan.Schumaker@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.