From: Valdis.Kletnieks@vt.edu
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Erez Zadok <ezk@cs.sunysb.edu>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
Pavel Emelyanov <xemul@openvz.org>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [NFS] NFSv2/3 broken exporting/mounting (permission denied) in 2.6.24-rc4
Date: Fri, 07 Dec 2007 15:38:44 -0500 [thread overview]
Message-ID: <4734.1197059924@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 07 Dec 2007 15:06:55 EST." <20071207200655.GD2204@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Fri, 07 Dec 2007 15:06:55 EST, "J. Bruce Fields" said:
> On Fri, Dec 07, 2007 at 03:00:13PM -0500, Erez Zadok wrote:
> > commit 2b1e300a9dfc3196ccddf6f1d74b91b7af55e416
> > Author: Eric W. Biederman <ebiederm@xmission.com>
> > Date: Sun Dec 2 00:33:17 2007 +1100
> Those files are actually in a separate filesystem (of type "nfsd") which
> is supposed to be mounted on /proc/fs/nfsd/. So that mount must have
> failed in the bad case? It's not immediately obvious to me what this
> patch has to do with that. Hm.
For what it's worth, the startup scripts for 'wine' and 'jexec' fail as well,
and at shutdown, I get complaints about being unable to dismount
/proc/sys/fs/binfmt_misc. 'strace' says:
open("/proc/sys/fs/binfmt_misc/windows", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EN
OENT (No such file or directory)
# grep binfmt /proc/mounts
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
I have to wonder if the fact there's 2 of them mounted is related to the
fact that 2 startup scripts tried to touch files under fs/binfmt_misc/ ?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-12-07 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 2:20 NFSv2/3 broken exporting/mounting (permission denied) in 2.6.24-rc4 Erez Zadok
2007-12-07 2:55 ` [NFS] " J. Bruce Fields
2007-12-07 20:00 ` Erez Zadok
2007-12-07 20:00 ` Erez Zadok
[not found] ` <200712072000.lB7K0DZ5013256-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2007-12-07 20:06 ` J. Bruce Fields
2007-12-07 20:06 ` J. Bruce Fields
2007-12-07 20:32 ` Erez Zadok
2007-12-07 20:32 ` Erez Zadok
2007-12-07 20:38 ` Valdis.Kletnieks
2007-12-07 20:38 ` Valdis.Kletnieks [this message]
2007-12-07 20:05 ` Erez Zadok
2007-12-07 20:05 ` Erez Zadok
[not found] ` <200712070220.lB72Kfqw004530-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2007-12-07 2:55 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2007-12-07 2:20 Erez Zadok
2007-12-07 10:54 Mikael Pettersson
[not found] ` <200712071054.lB7AscVW002471-gq7oiAaKCbRt3AgVzhmPzw@public.gmane.org>
2007-12-07 15:32 ` 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=4734.1197059924@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=ezk@cs.sunysb.edu \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nfs@lists.sourceforge.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=xemul@openvz.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.