> > The removal of /etc/mtab in favor of /proc/mounts is a new requirement,
> > and is not as trivial as you might hope. Internally the NFS client
> > represents the mount options as a binary data structure, and it contains
> > only the information that has traditionally been passed into the ke
> On Tue, 2007-07-31 at 17:16 -0400, Chuck Lever wrote:
> > Miklos Szeredi wrote:
> > > It would be nice to have all this stuff in 2.6.24, which doesn't leave
> > > a lot of time.
> >
> > Yes, that would be nice, but there's a lot of stuff that needs to get
> > done before this. NFS IPv6, for ex
On Tue, 2007-07-31 at 21:25 +0100, David Howells wrote:
> diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
> index 209d3a4..eaf9854 100644
> --- a/include/linux/page-flags.h
> +++ b/include/linux/page-flags.h
> @@ -83,19 +83,24 @@
> #define PG_private 11 /* If p
On Tue, Jul 31, 2007 at 10:19:57AM -0400, Chuck Lever wrote:
> The removal of /etc/mtab in favor of /proc/mounts is a new requirement,
> and is not as trivial as you might hope. Internally the NFS client
> represents the mount options as a binary data structure, and it contains
> only the infor
On Tue, 2007-07-31 at 17:16 -0400, Chuck Lever wrote:
> Miklos Szeredi wrote:
> > It would be nice to have all this stuff in 2.6.24, which doesn't leave
> > a lot of time.
>
> Yes, that would be nice, but there's a lot of stuff that needs to get
> done before this. NFS IPv6, for example, is a hi
Miklos Szeredi wrote:
After a successful mount, the NFS mount command tucks some options into
/etc/mtab that reflect which mountd was used for the mount, and what
protocol version and port was used for the mount request. Those options
are not passed to the kernel, and do not appear in /proc/mo
Relocate ROOT_NFS from below NFSD to be visibly part of NFS_FS group.
This makes the ROOT_NFS Kconfig option logically coherent.
Signed-off-by: Al Boldi <[EMAIL PROTECTED]>
Cc: Trond Myklebust <[EMAIL PROTECTED]>
---
--- a/fs/Kconfig2007-07-09 06:38:41.0 +0300
+++ b/fs/Kconfig
The attached patch makes it possible for the NFS filesystem to make use of the
network filesystem local caching service (FS-Cache).
To be able to use this, an updated mount program is required. This can be
obtained from:
http://people.redhat.com/steved/cachefs/util-linux/
To mount an NF
Get the SID under which the CacheFiles module should operate so that the
SELinux security system can control the accesses it makes.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
include/linux/security.h | 20
security/dummy.c |7 +++
security/selinux
Add an act-as SID to task_security_struct that is equivalent to fsuid/fsgid in
task_struct. This permits a task to perform operations as if it is the
overriding SID, without changing its own SID as that might be needed to control
access to the process by ptrace, signals, /proc, etc.
This is usefu
Permit an inode's security ID to be obtained by the CacheFiles module. This is
then used as the SID with which files and directories will be created in the
cache.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
include/linux/security.h | 13 +
security/dummy.c |6
Make it possible for a process's file creation SID to be temporarily overridden
by CacheFiles so that files created in the cache have the right label attached.
Without this facility, files created in the cache will be given the current
file creation SID of whatever process happens to have invoked
Add a function to install a monitor on the page lock waitqueue for a particular
page, thus allowing the page being unlocked to be detected.
This is used by CacheFiles to detect read completion on a page in the backing
filesystem so that it can then copy the data to the waiting netfs page.
Signed-
Export a number of functions for CacheFiles's use.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
fs/file_table.c |1 +
fs/super.c |2 ++
kernel/auditsc.c |2 ++
3 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/fs/file_table.c b/fs/file_table.c
index d17fd6
Add an address space operation to write one single page of data to an inode at
a page-aligned location (thus permitting the implementation to be highly
optimised).
This is used by CacheFiles to store the contents of netfs pages into their
backing file pages.
Supply a generic implementation for th
This one-line patch fixes the missing export of copy_page introduced
by the cachefile patches. This patch is not yet upstream, but is required
for cachefile on ia64. It will be pushed upstream when cachefile goes
upstream.
Signed-off-by: Prarit Bhargava <[EMAIL PROTECTED]>
Signed-Off-By: David H
Provide an add_wait_queue_tail() function to add a waiter to the back of a
wait queue instead of the front.
Signed-off-by: David Howells <[EMAIL PROTECTED]>
---
include/linux/wait.h |1 +
kernel/wait.c| 18 ++
2 files changed, 19 insertions(+), 0 deletions(-)
diff
Recruit a couple of page flags to aid in cache management. The following extra
flags are defined:
(1) PG_fscache (PG_owner_priv_2)
The marked page is backed by a local cache and is pinning resources in the
cache driver.
(2) PG_fscache_write (PG_owner_priv_3)
The marked page is
The attached patch causes read_cache_pages() to release page-private data on a
page for which add_to_page_cache() fails or the filler function fails. This
permits pages with caching references associated with them to be cleaned up.
The invalidatepage() address space op is called (indirectly) to do
These patches add local caching for network filesystems such as NFS and AFS.
This is a preview, so expect bugs.
FS-Cache now runs fully asynchronously as required by Trond Myklebust for NFS.
--
A tarball of the patches is available at:
http://people.redhat.com/~dhowells/fscache/patche
> >> After a successful mount, the NFS mount command tucks some options into
> >> /etc/mtab that reflect which mountd was used for the mount, and what
> >> protocol version and port was used for the mount request. Those options
> >> are not passed to the kernel, and do not appear in /proc/mount
> Really the only sane way of keeping track of whiteouts seems some external
> store. We did an experiment with Unionfs, and moving the whiteout handling
> to effectively a "library" that did all the dirty work cleaned up the code
> considerably [2,3].
What about keeping track of whiteouts in a sp
On Tue, Jul 31, 2007 at 06:03:06PM +0100, Mark Williamson wrote:
> > Really the only sane way of keeping track of whiteouts seems some external
> > store. We did an experiment with Unionfs, and moving the whiteout handling
> > to effectively a "library" that did all the dirty work cleaned up the co
On Tue, Jul 31, 2007 at 07:00:12PM +0200, Jan Blunck wrote:
> On Tue, Jul 31, Josef Sipek wrote:
>
> > On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
> > > Introduce white-out support to ext2.
> >
> > I think storing whiteouts on the branches is wrong. It creates all sort of
> > nast
On Tue, Jul 31, Josef Sipek wrote:
> On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
> > Introduce white-out support to ext2.
>
> I think storing whiteouts on the branches is wrong. It creates all sort of
> nasty cases when people actually try to use unioning. Imagine a (no-so
> unlik
On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
> Introduce white-out support to ext2.
I think storing whiteouts on the branches is wrong. It creates all sort of
nasty cases when people actually try to use unioning. Imagine a (no-so
unlikely) scenario where you have 2 unions, and they
Miklos Szeredi wrote:
After a successful mount, the NFS mount command tucks some options into
/etc/mtab that reflect which mountd was used for the mount, and what
protocol version and port was used for the mount request. Those options
are not passed to the kernel, and do not appear in /proc/mo
Hi Michael,
On Mon, Jul 30, 2007 at 09:43:08PM +0200, Michael Kerrisk wrote:
> Hello Amit.
>
> > On Mon, Jul 23, 2007 at 08:09:45AM +0200, Michael Kerrisk wrote:
> >> Amit,
> >>
> >> I've taken the page that you sent and made various minor formatting and
> >> wording fixes. I've also added vario
On Tue, Jul 31, 2007 at 09:44:36AM +0200, Jan Blunck wrote:
> Ok, this is pretty similar to the way I implemented this for tmpfs. The
> problem is that the union mount code is explicitly checking if the filesystem
> is supporting whiteout. I used to use a new filesystem flag (FS_WHITEOUT) for
> thi
On Tue, Jul 31, Andreas Dilger wrote:
> On Jul 31, 2007 09:44 +0200, Jan Blunck wrote:
> > Ok, this is pretty similar to the way I implemented this for tmpfs. The
> > problem is that the union mount code is explicitly checking if the
> > filesystem
> > is supporting whiteout. I used to use a new
> This patch contains implementation of show_options method for UFS,
> it depend on add-in-sunos-41x-compatible-mode-for-ufs.patch and
> add-in-sunos-41x-compatible-mode-for-ufs-fix.patch.
>
>
> Signed-off-by: Evgeniy Dushistov <[EMAIL PROTECTED]>
Thanks. I'll quite these up and submit them in
> After a successful mount, the NFS mount command tucks some options into
> /etc/mtab that reflect which mountd was used for the mount, and what
> protocol version and port was used for the mount request. Those options
> are not passed to the kernel, and do not appear in /proc/mounts today.
>
On Jul 31, 2007 09:44 +0200, Jan Blunck wrote:
> Ok, this is pretty similar to the way I implemented this for tmpfs. The
> problem is that the union mount code is explicitly checking if the filesystem
> is supporting whiteout. I used to use a new filesystem flag (FS_WHITEOUT) for
> this but though
On Mon, Jul 30, Theodore Tso wrote:
> On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
> > Introduce white-out support to ext2.
> >
> > Known Bugs:
> > - Needs a reserved inode number for white-outs
>
> You picked different reserved inodes for the ext2 and ext3
> filesystems. That's
34 matches
Mail list logo
