From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, nfsv4@linux-nfs.org,
Trond Myklebust <trond.myklebust@fys.uio.no>,
torvalds@osdl.org, linux-cachefs@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/7] Permit filesystem local caching and NFS superblock sharing [try #13]
Date: Sun, 03 Sep 2006 14:21:30 +0800 [thread overview]
Message-ID: <1157264490.3520.16.camel@raven.themaw.net> (raw)
In-Reply-To: <20060901225853.0171fd29.akpm@osdl.org>
On Fri, 2006-09-01 at 22:58 -0700, Andrew Morton wrote:
> > >
> > > It doesn't appear to be related to selinux.
I have a festering suspicion, but no evidence yet, that this is not
always the case.
> > >
> > > On a stock, mostly-up-to-date FC5 installation:
> > >
> > > echo 0 > /selinux/enforce
> > > service autofs stop
> > > service nfs stop
> > > service nfs start
> > > service autofs start
I'm now setup my little system the same.
[root@raven selinux]# uname -a
Linux raven.themaw.net 2.6.18-rc5-mm1 #1 SMP Sat Sep 2 23:11:01 WST 2006
x86_64 x86_64 x86_64 GNU/Linux
[root@raven selinux]# rpm -q autofs
autofs-4.1.4-29
[root@raven selinux]# getenforce
Permissive
[root@raven selinux]# rpm -q selinux-policy
selinux-policy-2.3.7-2.fc5
> > >
> > >
> > > sony:/home/akpm> ls -l /net/bix/usr/src
> > > total 0
> > >
> > > sony:/home/akpm> showmount -e bix
> > > Export list for bix:
> > > / *
> > > /usr/src *
> > > /mnt/export *
Almost the same.
[root@raven selinux]# showmount -e budgie
Export list for budgie:
/ *
/usr/src *
> > >
> > >
> > > The automounter will mount bix:/ on /net/bix. But I am unable to get it to
> > > mount bix's /usr/src on /net/bix/usr/src.
> >
> > Is it the same symptom as before or is it that bix:/usr/src is not also
> > being mounted?
[root@raven selinux]# lsmod|grep autofs
autofs4 40776 1
I guess you haven't got the autofs module loaded instead of autofs4 by
mistake.
[raven@raven ~]$ mount
/dev/hda5 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda6 on /home type ext3 (rw)
/dev/hda7 on /work type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
automount(pid3463) on /net type autofs
(rw,fd=5,pgrp=3463,minproto=2,maxproto=4)
[raven@raven ~]$ ls /net/budgie
autofs cdrom export71 initrd lib opt sbin usr
vmlinuz.old
bin dev floppy initrd.img lost+found proc sys var
boot etc home initrd.img.old mnt root tmp vmlinuz
[raven@raven ~]$ mount
/dev/hda5 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda6 on /home type ext3 (rw)
/dev/hda7 on /work type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
automount(pid3463) on /net type autofs
(rw,fd=5,pgrp=3463,minproto=2,maxproto=4)
budgie:/ on /net/budgie type nfs
(rw,nosuid,nodev,hard,intr,addr=10.49.97.33)
budgie:/usr/src on /net/budgie/usr/src type nfs
(rw,nosuid,nodev,hard,intr,addr=10.49.97.33)
So I wonder what the different is between the setups?
>
> When this saga first started an `ls -l /net/bix' showed a corrupted dentry
> for /net/bix/usr. It was determined that this was SELinux-related. Fixes were
> made and that no longer occurs.
>
> Now, treading on /net/bix/usr/src does not cause bix:/usr/src to be mounted
> at /net/bix/usr/src. Without git-nfs that mount does occur.
>
> The present behaviour is unchanged if /selinux/enforce is set to 0.
>
> > > Without git-nfs applied, /net/bix/usr/src mounts as expected.
> > >
> > > iirc, we decided this is related to the fs-cache infrastructure work which
> > > went into git-nfs. I think David can reproduce this?
Can you reproduce this David?
> >
> > I'll build the latest mm kernel and try to reproduce it.
> > >From memory I couldn't reproduce it last time I tried.
> > Is there anything I need to add to rc5-mm1 for this?
>
> Nope.
I'm stumped.
Ian
next prev parent reply other threads:[~2006-09-03 6:21 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 19:31 [PATCH 0/7] Permit filesystem local caching and NFS superblock sharing [try #13] David Howells
2006-08-30 19:31 ` [PATCH 1/7] FS-Cache: Provide a filesystem-specific sync'able page bit " David Howells
2006-08-30 19:31 ` [PATCH 2/7] FS-Cache: Generic filesystem caching facility " David Howells
2006-08-30 19:32 ` [PATCH 3/7] FS-Cache: Release page->private after failed readahead " David Howells
2006-08-30 19:32 ` [PATCH 4/7] FS-Cache: Make kAFS use FS-Cache " David Howells
2006-08-30 19:32 ` [PATCH 5/7] NFS: Use local caching " David Howells
2006-08-30 19:32 ` [PATCH 6/7] FS-Cache: CacheFiles: ia64: missing copy_page export " David Howells
2006-08-30 19:32 ` [PATCH 7/7] FS-Cache: CacheFiles: A cache that backs onto a mounted filesystem " David Howells
2006-08-30 19:52 ` [PATCH 0/7] Permit filesystem local caching and NFS superblock sharing " Andrew Morton
2006-08-30 20:37 ` David Howells
2006-08-30 20:55 ` Andrew Morton
2006-08-31 9:58 ` David Howells
2006-08-31 17:21 ` Andrew Morton
2006-08-31 17:26 ` Trond Myklebust
2006-08-31 17:42 ` David Howells
2006-08-31 18:04 ` Andrew Morton
2006-09-01 13:08 ` David Howells
2006-09-01 16:34 ` Andrew Morton
2006-09-01 17:00 ` Trond Myklebust
2006-09-02 2:50 ` Andrew Morton
2006-09-02 4:11 ` Ian Kent
2006-09-02 5:58 ` Andrew Morton
2006-09-03 6:21 ` Ian Kent [this message]
2006-09-03 6:30 ` Andrew Morton
2006-09-03 6:43 ` Ian Kent
2006-09-03 16:58 ` Andrew Morton
2006-09-04 2:23 ` Ian Kent
2006-09-04 5:40 ` Ian Kent
2006-09-02 4:49 ` Ian Kent
2006-09-04 11:52 ` David Howells
2006-09-04 11:52 ` David Howells
2006-09-04 13:24 ` Ian Kent
2006-09-05 1:57 ` Trond Myklebust
2006-09-05 2:55 ` Ian Kent
2006-09-05 3:50 ` Trond Myklebust
2006-09-05 4:03 ` Ian Kent
2006-09-05 4:53 ` Trond Myklebust
2006-09-05 6:06 ` Ian Kent
2006-09-05 7:01 ` Ian Kent
2006-09-05 12:52 ` Trond Myklebust
2006-09-06 4:54 ` Ian Kent
2006-09-05 9:40 ` David Howells
2006-09-05 10:20 ` Ian Kent
2006-09-05 10:37 ` David Howells
2006-09-05 12:20 ` Ian Kent
2006-09-05 13:38 ` David Howells
2006-09-06 4:58 ` Ian Kent
2006-09-06 9:51 ` David Howells
2006-09-06 12:46 ` Trond Myklebust
2006-09-06 13:24 ` David Howells
2006-09-07 5:30 ` Ian Kent
2006-09-07 6:17 ` Trond Myklebust
2006-09-07 7:40 ` Ian Kent
2006-09-05 9:48 ` David Howells
2006-09-05 10:14 ` Ian Kent
2006-09-05 9:57 ` David Howells
2006-09-05 12:47 ` Trond Myklebust
2006-09-05 12:53 ` Trond Myklebust
2006-09-05 13:40 ` David Howells
2006-09-06 10:27 ` Ian Kent
2006-09-04 13:46 ` David Howells
2006-09-04 15:00 ` Ian Kent
2006-09-05 4:11 ` Ian Kent
2006-09-05 4:17 ` Trond Myklebust
2006-09-05 2:23 ` Trond Myklebust
2006-09-05 3:01 ` Ian Kent
2006-09-05 4:05 ` Trond Myklebust
2006-09-05 4:06 ` Ian Kent
2006-09-05 4:57 ` Trond Myklebust
2006-09-05 6:45 ` Ian Kent
2006-09-05 7:07 ` Ian Kent
2006-09-04 18:20 ` David Howells
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=1157264490.3520.16.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=akpm@osdl.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).