2007-04-26 22:49:28 +00:00
|
|
|
/* /proc interface for AFS
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
|
|
|
* Copyright (C) 2002 Red Hat, Inc. All Rights Reserved.
|
|
|
|
* Written by David Howells (dhowells@redhat.com)
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License
|
|
|
|
* as published by the Free Software Foundation; either version
|
|
|
|
* 2 of the License, or (at your option) any later version.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/proc_fs.h>
|
|
|
|
#include <linux/seq_file.h>
|
Detach sched.h from mm.h
First thing mm.h does is including sched.h solely for can_do_mlock() inline
function which has "current" dereference inside. By dealing with can_do_mlock()
mm.h can be detached from sched.h which is good. See below, why.
This patch
a) removes unconditional inclusion of sched.h from mm.h
b) makes can_do_mlock() normal function in mm/mlock.c
c) exports can_do_mlock() to not break compilation
d) adds sched.h inclusions back to files that were getting it indirectly.
e) adds less bloated headers to some files (asm/signal.h, jiffies.h) that were
getting them indirectly
Net result is:
a) mm.h users would get less code to open, read, preprocess, parse, ... if
they don't need sched.h
b) sched.h stops being dependency for significant number of files:
on x86_64 allmodconfig touching sched.h results in recompile of 4083 files,
after patch it's only 3744 (-8.3%).
Cross-compile tested on
all arm defconfigs, all mips defconfigs, all powerpc defconfigs,
alpha alpha-up
arm
i386 i386-up i386-defconfig i386-allnoconfig
ia64 ia64-up
m68k
mips
parisc parisc-up
powerpc powerpc-up
s390 s390-up
sparc sparc-up
sparc64 sparc64-up
um-x86_64
x86_64 x86_64-up x86_64-defconfig x86_64-allnoconfig
as well as my two usual configs.
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-20 21:22:52 +00:00
|
|
|
#include <linux/sched.h>
|
2016-12-24 19:46:01 +00:00
|
|
|
#include <linux/uaccess.h>
|
2005-04-16 22:20:36 +00:00
|
|
|
#include "internal.h"
|
|
|
|
|
2017-11-02 15:27:45 +00:00
|
|
|
static inline struct afs_net *afs_proc2net(struct file *f)
|
|
|
|
{
|
|
|
|
return &__afs_net;
|
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2017-11-02 15:27:45 +00:00
|
|
|
static inline struct afs_net *afs_seq2net(struct seq_file *m)
|
|
|
|
{
|
|
|
|
return &__afs_net; // TODO: use seq_file_net(m)
|
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
static void *afs_proc_cells_start(struct seq_file *p, loff_t *pos);
|
|
|
|
static void *afs_proc_cells_next(struct seq_file *p, void *v, loff_t *pos);
|
|
|
|
static void afs_proc_cells_stop(struct seq_file *p, void *v);
|
|
|
|
static int afs_proc_cells_show(struct seq_file *m, void *v);
|
|
|
|
|
2009-09-22 23:43:43 +00:00
|
|
|
static const struct seq_operations afs_proc_cells_ops = {
|
2005-04-16 22:20:36 +00:00
|
|
|
.start = afs_proc_cells_start,
|
|
|
|
.next = afs_proc_cells_next,
|
|
|
|
.stop = afs_proc_cells_stop,
|
|
|
|
.show = afs_proc_cells_show,
|
|
|
|
};
|
|
|
|
|
|
|
|
static void *afs_proc_cell_volumes_start(struct seq_file *p, loff_t *pos);
|
|
|
|
static void *afs_proc_cell_volumes_next(struct seq_file *p, void *v,
|
|
|
|
loff_t *pos);
|
|
|
|
static void afs_proc_cell_volumes_stop(struct seq_file *p, void *v);
|
|
|
|
static int afs_proc_cell_volumes_show(struct seq_file *m, void *v);
|
|
|
|
|
2009-09-22 23:43:43 +00:00
|
|
|
static const struct seq_operations afs_proc_cell_volumes_ops = {
|
2005-04-16 22:20:36 +00:00
|
|
|
.start = afs_proc_cell_volumes_start,
|
|
|
|
.next = afs_proc_cell_volumes_next,
|
|
|
|
.stop = afs_proc_cell_volumes_stop,
|
|
|
|
.show = afs_proc_cell_volumes_show,
|
|
|
|
};
|
|
|
|
|
|
|
|
static void *afs_proc_cell_vlservers_start(struct seq_file *p, loff_t *pos);
|
|
|
|
static void *afs_proc_cell_vlservers_next(struct seq_file *p, void *v,
|
|
|
|
loff_t *pos);
|
|
|
|
static void afs_proc_cell_vlservers_stop(struct seq_file *p, void *v);
|
|
|
|
static int afs_proc_cell_vlservers_show(struct seq_file *m, void *v);
|
|
|
|
|
2009-09-22 23:43:43 +00:00
|
|
|
static const struct seq_operations afs_proc_cell_vlservers_ops = {
|
2005-04-16 22:20:36 +00:00
|
|
|
.start = afs_proc_cell_vlservers_start,
|
|
|
|
.next = afs_proc_cell_vlservers_next,
|
|
|
|
.stop = afs_proc_cell_vlservers_stop,
|
|
|
|
.show = afs_proc_cell_vlservers_show,
|
|
|
|
};
|
|
|
|
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
static void *afs_proc_servers_start(struct seq_file *p, loff_t *pos);
|
|
|
|
static void *afs_proc_servers_next(struct seq_file *p, void *v,
|
2005-04-16 22:20:36 +00:00
|
|
|
loff_t *pos);
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
static void afs_proc_servers_stop(struct seq_file *p, void *v);
|
|
|
|
static int afs_proc_servers_show(struct seq_file *m, void *v);
|
|
|
|
|
|
|
|
static const struct seq_operations afs_proc_servers_ops = {
|
|
|
|
.start = afs_proc_servers_start,
|
|
|
|
.next = afs_proc_servers_next,
|
|
|
|
.stop = afs_proc_servers_stop,
|
|
|
|
.show = afs_proc_servers_show,
|
2005-04-16 22:20:36 +00:00
|
|
|
};
|
|
|
|
|
2018-04-09 20:12:31 +00:00
|
|
|
static void *afs_proc_sysname_start(struct seq_file *p, loff_t *pos);
|
|
|
|
static void *afs_proc_sysname_next(struct seq_file *p, void *v,
|
|
|
|
loff_t *pos);
|
|
|
|
static void afs_proc_sysname_stop(struct seq_file *p, void *v);
|
|
|
|
static int afs_proc_sysname_show(struct seq_file *m, void *v);
|
|
|
|
|
|
|
|
static const struct seq_operations afs_proc_sysname_ops = {
|
|
|
|
.start = afs_proc_sysname_start,
|
|
|
|
.next = afs_proc_sysname_next,
|
|
|
|
.stop = afs_proc_sysname_stop,
|
|
|
|
.show = afs_proc_sysname_show,
|
|
|
|
};
|
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
/*
|
|
|
|
* display a header line followed by a load of cell lines
|
|
|
|
*/
|
|
|
|
static int afs_proc_cells_show(struct seq_file *m, void *v)
|
|
|
|
{
|
|
|
|
struct afs_cell *cell = list_entry(v, struct afs_cell, proc_link);
|
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
|
|
|
|
if (v == &net->proc_cells) {
|
|
|
|
/* display header on line 1 */
|
|
|
|
seq_puts(m, "USE NAME\n");
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* display one cell per line on subsequent lines */
|
|
|
|
seq_printf(m, "%3u %s\n", atomic_read(&cell->usage), cell->name);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* set up the iterator to start reading from the cells list and return the
|
|
|
|
* first item
|
|
|
|
*/
|
|
|
|
static void *afs_proc_cells_start(struct seq_file *m, loff_t *_pos)
|
2018-04-09 20:12:31 +00:00
|
|
|
__acquires(rcu)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2017-11-02 15:27:45 +00:00
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
rcu_read_lock();
|
2017-11-02 15:27:45 +00:00
|
|
|
return seq_list_start_head(&net->proc_cells, *_pos);
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* move to next cell in cells list
|
|
|
|
*/
|
2017-11-02 15:27:45 +00:00
|
|
|
static void *afs_proc_cells_next(struct seq_file *m, void *v, loff_t *pos)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2017-11-02 15:27:45 +00:00
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
|
|
|
|
return seq_list_next(v, &net->proc_cells, pos);
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* clean up after reading from the cells list
|
|
|
|
*/
|
2017-11-02 15:27:45 +00:00
|
|
|
static void afs_proc_cells_stop(struct seq_file *m, void *v)
|
2018-04-09 20:12:31 +00:00
|
|
|
__releases(rcu)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2017-11-02 15:27:50 +00:00
|
|
|
rcu_read_unlock();
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* handle writes to /proc/fs/afs/cells
|
|
|
|
* - to add cells: echo "add <cellname> <IP>[:<IP>][:<IP>]"
|
|
|
|
*/
|
|
|
|
static ssize_t afs_proc_cells_write(struct file *file, const char __user *buf,
|
|
|
|
size_t size, loff_t *_pos)
|
|
|
|
{
|
2017-11-02 15:27:45 +00:00
|
|
|
struct afs_net *net = afs_proc2net(file);
|
2005-04-16 22:20:36 +00:00
|
|
|
char *kbuf, *name, *args;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
/* start by dragging the command into memory */
|
|
|
|
if (size <= 1 || size >= PAGE_SIZE)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2015-12-24 05:06:05 +00:00
|
|
|
kbuf = memdup_user_nul(buf, size);
|
|
|
|
if (IS_ERR(kbuf))
|
|
|
|
return PTR_ERR(kbuf);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/* trim to first NL */
|
|
|
|
name = memchr(kbuf, '\n', size);
|
|
|
|
if (name)
|
|
|
|
*name = 0;
|
|
|
|
|
|
|
|
/* split into command, name and argslist */
|
|
|
|
name = strchr(kbuf, ' ');
|
|
|
|
if (!name)
|
|
|
|
goto inval;
|
|
|
|
do {
|
|
|
|
*name++ = 0;
|
|
|
|
} while(*name == ' ');
|
|
|
|
if (!*name)
|
|
|
|
goto inval;
|
|
|
|
|
|
|
|
args = strchr(name, ' ');
|
|
|
|
if (!args)
|
|
|
|
goto inval;
|
|
|
|
do {
|
|
|
|
*args++ = 0;
|
|
|
|
} while(*args == ' ');
|
|
|
|
if (!*args)
|
|
|
|
goto inval;
|
|
|
|
|
|
|
|
/* determine command to perform */
|
|
|
|
_debug("cmd=%s name=%s args=%s", kbuf, name, args);
|
|
|
|
|
|
|
|
if (strcmp(kbuf, "add") == 0) {
|
|
|
|
struct afs_cell *cell;
|
2007-04-26 22:55:03 +00:00
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
cell = afs_lookup_cell(net, name, strlen(name), args, true);
|
2007-04-26 22:55:03 +00:00
|
|
|
if (IS_ERR(cell)) {
|
|
|
|
ret = PTR_ERR(cell);
|
2005-04-16 22:20:36 +00:00
|
|
|
goto done;
|
2007-04-26 22:55:03 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-04-09 20:12:31 +00:00
|
|
|
if (test_and_set_bit(AFS_CELL_FL_NO_GC, &cell->flags))
|
|
|
|
afs_put_cell(net, cell);
|
2005-04-16 22:20:36 +00:00
|
|
|
printk("kAFS: Added new cell '%s'\n", name);
|
2007-04-26 22:49:28 +00:00
|
|
|
} else {
|
2005-04-16 22:20:36 +00:00
|
|
|
goto inval;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = size;
|
|
|
|
|
2007-04-26 22:49:28 +00:00
|
|
|
done:
|
2005-04-16 22:20:36 +00:00
|
|
|
kfree(kbuf);
|
|
|
|
_leave(" = %d", ret);
|
|
|
|
return ret;
|
|
|
|
|
2007-04-26 22:49:28 +00:00
|
|
|
inval:
|
2005-04-16 22:20:36 +00:00
|
|
|
ret = -EINVAL;
|
|
|
|
printk("kAFS: Invalid Command on /proc/fs/afs/cells file\n");
|
|
|
|
goto done;
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
static int afs_proc_cells_open(struct inode *inode, struct file *file)
|
|
|
|
{
|
|
|
|
return seq_open(file, &afs_proc_cells_ops);
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct file_operations afs_proc_cells_fops = {
|
|
|
|
.open = afs_proc_cells_open,
|
|
|
|
.read = seq_read,
|
|
|
|
.write = afs_proc_cells_write,
|
|
|
|
.llseek = seq_lseek,
|
|
|
|
.release = seq_release,
|
|
|
|
};
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
static ssize_t afs_proc_rootcell_read(struct file *file, char __user *buf,
|
|
|
|
size_t size, loff_t *_pos)
|
|
|
|
{
|
2018-04-06 13:17:23 +00:00
|
|
|
struct afs_cell *cell;
|
|
|
|
struct afs_net *net = afs_proc2net(file);
|
|
|
|
unsigned int seq = 0;
|
|
|
|
char name[AFS_MAXCELLNAME + 1];
|
|
|
|
int len;
|
|
|
|
|
|
|
|
if (*_pos > 0)
|
|
|
|
return 0;
|
|
|
|
if (!net->ws_cell)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
rcu_read_lock();
|
|
|
|
do {
|
|
|
|
read_seqbegin_or_lock(&net->cells_lock, &seq);
|
|
|
|
len = 0;
|
|
|
|
cell = rcu_dereference_raw(net->ws_cell);
|
|
|
|
if (cell) {
|
|
|
|
len = cell->name_len;
|
|
|
|
memcpy(name, cell->name, len);
|
|
|
|
}
|
|
|
|
} while (need_seqretry(&net->cells_lock, seq));
|
|
|
|
done_seqretry(&net->cells_lock, seq);
|
|
|
|
rcu_read_unlock();
|
|
|
|
|
|
|
|
if (!len)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
name[len++] = '\n';
|
|
|
|
if (len > size)
|
|
|
|
len = size;
|
|
|
|
if (copy_to_user(buf, name, len) != 0)
|
|
|
|
return -EFAULT;
|
|
|
|
*_pos = 1;
|
|
|
|
return len;
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* handle writes to /proc/fs/afs/rootcell
|
|
|
|
* - to initialize rootcell: echo "cell.name:192.168.231.14"
|
|
|
|
*/
|
|
|
|
static ssize_t afs_proc_rootcell_write(struct file *file,
|
|
|
|
const char __user *buf,
|
|
|
|
size_t size, loff_t *_pos)
|
|
|
|
{
|
2017-11-02 15:27:45 +00:00
|
|
|
struct afs_net *net = afs_proc2net(file);
|
2005-04-16 22:20:36 +00:00
|
|
|
char *kbuf, *s;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
/* start by dragging the command into memory */
|
|
|
|
if (size <= 1 || size >= PAGE_SIZE)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2015-12-24 05:06:05 +00:00
|
|
|
kbuf = memdup_user_nul(buf, size);
|
|
|
|
if (IS_ERR(kbuf))
|
|
|
|
return PTR_ERR(kbuf);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-04-09 20:12:31 +00:00
|
|
|
ret = -EINVAL;
|
|
|
|
if (kbuf[0] == '.')
|
|
|
|
goto out;
|
|
|
|
if (memchr(kbuf, '/', size))
|
|
|
|
goto out;
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/* trim to first NL */
|
|
|
|
s = memchr(kbuf, '\n', size);
|
|
|
|
if (s)
|
|
|
|
*s = 0;
|
|
|
|
|
|
|
|
/* determine command to perform */
|
|
|
|
_debug("rootcell=%s", kbuf);
|
|
|
|
|
2017-11-02 15:27:45 +00:00
|
|
|
ret = afs_cell_init(net, kbuf);
|
2005-04-16 22:20:36 +00:00
|
|
|
if (ret >= 0)
|
|
|
|
ret = size; /* consume everything, always */
|
|
|
|
|
2018-04-09 20:12:31 +00:00
|
|
|
out:
|
2005-04-16 22:20:36 +00:00
|
|
|
kfree(kbuf);
|
|
|
|
_leave(" = %d", ret);
|
|
|
|
return ret;
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
static const struct file_operations afs_proc_rootcell_fops = {
|
|
|
|
.read = afs_proc_rootcell_read,
|
|
|
|
.write = afs_proc_rootcell_write,
|
|
|
|
.llseek = no_llseek,
|
|
|
|
};
|
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
static const char afs_vol_types[3][3] = {
|
|
|
|
[AFSVL_RWVOL] = "RW",
|
|
|
|
[AFSVL_ROVOL] = "RO",
|
|
|
|
[AFSVL_BACKVOL] = "BK",
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* display a header line followed by a load of volume lines
|
|
|
|
*/
|
|
|
|
static int afs_proc_cell_volumes_show(struct seq_file *m, void *v)
|
|
|
|
{
|
|
|
|
struct afs_cell *cell = PDE_DATA(file_inode(m->file));
|
|
|
|
struct afs_volume *vol = list_entry(v, struct afs_volume, proc_link);
|
|
|
|
|
|
|
|
/* Display header on line 1 */
|
|
|
|
if (v == &cell->proc_volumes) {
|
|
|
|
seq_puts(m, "USE VID TY\n");
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
seq_printf(m, "%3d %08x %s\n",
|
|
|
|
atomic_read(&vol->usage), vol->vid,
|
|
|
|
afs_vol_types[vol->type]);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* set up the iterator to start reading from the cells list and return the
|
|
|
|
* first item
|
|
|
|
*/
|
|
|
|
static void *afs_proc_cell_volumes_start(struct seq_file *m, loff_t *_pos)
|
2018-04-09 20:12:31 +00:00
|
|
|
__acquires(cell->proc_lock)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2018-04-13 18:45:09 +00:00
|
|
|
struct afs_cell *cell = PDE_DATA(file_inode(m->file));
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
_enter("cell=%p pos=%Ld", cell, *_pos);
|
|
|
|
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
read_lock(&cell->proc_lock);
|
|
|
|
return seq_list_start_head(&cell->proc_volumes, *_pos);
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* move to next cell in cells list
|
|
|
|
*/
|
|
|
|
static void *afs_proc_cell_volumes_next(struct seq_file *p, void *v,
|
|
|
|
loff_t *_pos)
|
|
|
|
{
|
2018-04-13 18:45:09 +00:00
|
|
|
struct afs_cell *cell = PDE_DATA(file_inode(p->file));
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
_enter("cell=%p pos=%Ld", cell, *_pos);
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
return seq_list_next(v, &cell->proc_volumes, _pos);
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* clean up after reading from the cells list
|
|
|
|
*/
|
|
|
|
static void afs_proc_cell_volumes_stop(struct seq_file *p, void *v)
|
2018-04-09 20:12:31 +00:00
|
|
|
__releases(cell->proc_lock)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2018-04-13 18:45:09 +00:00
|
|
|
struct afs_cell *cell = PDE_DATA(file_inode(p->file));
|
2005-04-16 22:20:36 +00:00
|
|
|
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
read_unlock(&cell->proc_lock);
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* display a header line followed by a load of volume lines
|
|
|
|
*/
|
2018-05-18 10:46:14 +00:00
|
|
|
static int afs_proc_cell_vlservers_show(struct seq_file *m, void *v)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2018-05-18 10:46:14 +00:00
|
|
|
struct sockaddr_rxrpc *addr = v;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
/* display header on line 1 */
|
|
|
|
if (v == (void *)1) {
|
|
|
|
seq_puts(m, "ADDRESS\n");
|
2005-04-16 22:20:36 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
/* display one cell per line on subsequent lines */
|
|
|
|
seq_printf(m, "%pISp\n", &addr->transport);
|
2005-04-16 22:20:36 +00:00
|
|
|
return 0;
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* set up the iterator to start reading from the cells list and return the
|
|
|
|
* first item
|
|
|
|
*/
|
|
|
|
static void *afs_proc_cell_vlservers_start(struct seq_file *m, loff_t *_pos)
|
2018-04-09 20:12:31 +00:00
|
|
|
__acquires(rcu)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2017-11-02 15:27:50 +00:00
|
|
|
struct afs_addr_list *alist;
|
2018-04-13 18:45:09 +00:00
|
|
|
struct afs_cell *cell = PDE_DATA(file_inode(m->file));
|
2005-04-16 22:20:36 +00:00
|
|
|
loff_t pos = *_pos;
|
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
rcu_read_lock();
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
alist = rcu_dereference(cell->vl_addrs);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/* allow for the header line */
|
|
|
|
if (!pos)
|
|
|
|
return (void *) 1;
|
|
|
|
pos--;
|
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
if (!alist || pos >= alist->nr_addrs)
|
2005-04-16 22:20:36 +00:00
|
|
|
return NULL;
|
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
return alist->addrs + pos;
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* move to next cell in cells list
|
|
|
|
*/
|
|
|
|
static void *afs_proc_cell_vlservers_next(struct seq_file *p, void *v,
|
|
|
|
loff_t *_pos)
|
|
|
|
{
|
2017-11-02 15:27:50 +00:00
|
|
|
struct afs_addr_list *alist;
|
2018-04-13 18:45:09 +00:00
|
|
|
struct afs_cell *cell = PDE_DATA(file_inode(p->file));
|
2005-04-16 22:20:36 +00:00
|
|
|
loff_t pos;
|
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
alist = rcu_dereference(cell->vl_addrs);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
pos = *_pos;
|
|
|
|
(*_pos)++;
|
2017-11-02 15:27:50 +00:00
|
|
|
if (!alist || pos >= alist->nr_addrs)
|
2005-04-16 22:20:36 +00:00
|
|
|
return NULL;
|
|
|
|
|
2017-11-02 15:27:50 +00:00
|
|
|
return alist->addrs + pos;
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* clean up after reading from the cells list
|
|
|
|
*/
|
|
|
|
static void afs_proc_cell_vlservers_stop(struct seq_file *p, void *v)
|
2018-04-09 20:12:31 +00:00
|
|
|
__releases(rcu)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2017-11-02 15:27:50 +00:00
|
|
|
rcu_read_unlock();
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* display a header line followed by a load of volume lines
|
|
|
|
*/
|
2018-05-18 10:46:14 +00:00
|
|
|
static int afs_proc_servers_show(struct seq_file *m, void *v)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2018-05-18 10:46:14 +00:00
|
|
|
struct afs_server *server;
|
|
|
|
struct afs_addr_list *alist;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
if (v == SEQ_START_TOKEN) {
|
|
|
|
seq_puts(m, "UUID USE ADDR\n");
|
2005-04-16 22:20:36 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
server = list_entry(v, struct afs_server, proc_link);
|
|
|
|
alist = rcu_dereference(server->addresses);
|
|
|
|
seq_printf(m, "%pU %3d %pISp\n",
|
|
|
|
&server->uuid,
|
|
|
|
atomic_read(&server->usage),
|
|
|
|
&alist->addrs[alist->index].transport);
|
2005-04-16 22:20:36 +00:00
|
|
|
return 0;
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
* Set up the iterator to start reading from the server list and return the
|
|
|
|
* first item.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
static void *afs_proc_servers_start(struct seq_file *m, loff_t *_pos)
|
2018-04-09 20:12:31 +00:00
|
|
|
__acquires(rcu)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
struct afs_net *net = afs_seq2net(m);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
rcu_read_lock();
|
|
|
|
return seq_hlist_start_head_rcu(&net->fs_proc, *_pos);
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* move to next cell in cells list
|
|
|
|
*/
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
static void *afs_proc_servers_next(struct seq_file *m, void *v, loff_t *_pos)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
struct afs_net *net = afs_seq2net(m);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
return seq_hlist_next_rcu(v, &net->fs_proc, _pos);
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* clean up after reading from the cells list
|
|
|
|
*/
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
static void afs_proc_servers_stop(struct seq_file *p, void *v)
|
2018-04-09 20:12:31 +00:00
|
|
|
__releases(rcu)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
afs: Overhaul volume and server record caching and fileserver rotation
The current code assumes that volumes and servers are per-cell and are
never shared, but this is not enforced, and, indeed, public cells do exist
that are aliases of each other. Further, an organisation can, say, set up
a public cell and a private cell with overlapping, but not identical, sets
of servers. The difference is purely in the database attached to the VL
servers.
The current code will malfunction if it sees a server in two cells as it
assumes global address -> server record mappings and that each server is in
just one cell.
Further, each server may have multiple addresses - and may have addresses
of different families (IPv4 and IPv6, say).
To this end, the following structural changes are made:
(1) Server record management is overhauled:
(a) Server records are made independent of cell. The namespace keeps
track of them, volume records have lists of them and each vnode
has a server on which its callback interest currently resides.
(b) The cell record no longer keeps a list of servers known to be in
that cell.
(c) The server records are now kept in a flat list because there's no
single address to sort on.
(d) Server records are now keyed by their UUID within the namespace.
(e) The addresses for a server are obtained with the VL.GetAddrsU
rather than with VL.GetEntryByName, using the server's UUID as a
parameter.
(f) Cached server records are garbage collected after a period of
non-use and are counted out of existence before purging is allowed
to complete. This protects the work functions against rmmod.
(g) The servers list is now in /proc/fs/afs/servers.
(2) Volume record management is overhauled:
(a) An RCU-replaceable server list is introduced. This tracks both
servers and their coresponding callback interests.
(b) The superblock is now keyed on cell record and numeric volume ID.
(c) The volume record is now tied to the superblock which mounts it,
and is activated when mounted and deactivated when unmounted.
This makes it easier to handle the cache cookie without causing a
double-use in fscache.
(d) The volume record is loaded from the VLDB using VL.GetEntryByNameU
to get the server UUID list.
(e) The volume name is updated if it is seen to have changed when the
volume is updated (the update is keyed on the volume ID).
(3) The vlocation record is got rid of and VLDB records are no longer
cached. Sufficient information is stored in the volume record, though
an update to a volume record is now no longer shared between related
volumes (volumes come in bundles of three: R/W, R/O and backup).
and the following procedural changes are made:
(1) The fileserver cursor introduced previously is now fleshed out and
used to iterate over fileservers and their addresses.
(2) Volume status is checked during iteration, and the server list is
replaced if a change is detected.
(3) Server status is checked during iteration, and the address list is
replaced if a change is detected.
(4) The abort code is saved into the address list cursor and -ECONNABORTED
returned in afs_make_call() if a remote abort happened rather than
translating the abort into an error message. This allows actions to
be taken depending on the abort code more easily.
(a) If a VMOVED abort is seen then this is handled by rechecking the
volume and restarting the iteration.
(b) If a VBUSY, VRESTARTING or VSALVAGING abort is seen then this is
handled by sleeping for a short period and retrying and/or trying
other servers that might serve that volume. A message is also
displayed once until the condition has cleared.
(c) If a VOFFLINE abort is seen, then this is handled as VBUSY for the
moment.
(d) If a VNOVOL abort is seen, the volume is rechecked in the VLDB to
see if it has been deleted; if not, the fileserver is probably
indicating that the volume couldn't be attached and needs
salvaging.
(e) If statfs() sees one of these aborts, it does not sleep, but
rather returns an error, so as not to block the umount program.
(5) The fileserver iteration functions in vnode.c are now merged into
their callers and more heavily macroised around the cursor. vnode.c
is removed.
(6) Operations on a particular vnode are serialised on that vnode because
the server will lock that vnode whilst it operates on it, so a second
op sent will just have to wait.
(7) Fileservers are probed with FS.GetCapabilities before being used.
This is where service upgrade will be done.
(8) A callback interest on a fileserver is set up before an FS operation
is performed and passed through to afs_make_call() so that it can be
set on the vnode if the operation returns a callback. The callback
interest is passed through to afs_iget() also so that it can be set
there too.
In general, record updating is done on an as-needed basis when we try to
access servers, volumes or vnodes rather than offloading it to work items
and special threads.
Notes:
(1) Pre AFS-3.4 servers are no longer supported, though this can be added
back if necessary (AFS-3.4 was released in 1998).
(2) VBUSY is retried forever for the moment at intervals of 1s.
(3) /proc/fs/afs/<cell>/servers no longer exists.
Signed-off-by: David Howells <dhowells@redhat.com>
2017-11-02 15:27:50 +00:00
|
|
|
rcu_read_unlock();
|
2007-04-26 22:49:28 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-04-09 20:12:31 +00:00
|
|
|
void afs_put_sysnames(struct afs_sysnames *sysnames)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
if (sysnames && refcount_dec_and_test(&sysnames->usage)) {
|
|
|
|
for (i = 0; i < sysnames->nr; i++)
|
|
|
|
if (sysnames->subs[i] != afs_init_sysname &&
|
|
|
|
sysnames->subs[i] != sysnames->blank)
|
|
|
|
kfree(sysnames->subs[i]);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Handle opening of /proc/fs/afs/sysname. If it is opened for writing, we
|
|
|
|
* assume the caller wants to change the substitution list and we allocate a
|
|
|
|
* buffer to hold the list.
|
|
|
|
*/
|
|
|
|
static int afs_proc_sysname_open(struct inode *inode, struct file *file)
|
|
|
|
{
|
|
|
|
struct afs_sysnames *sysnames;
|
|
|
|
struct seq_file *m;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
ret = seq_open(file, &afs_proc_sysname_ops);
|
|
|
|
if (ret < 0)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
if (file->f_mode & FMODE_WRITE) {
|
|
|
|
sysnames = kzalloc(sizeof(*sysnames), GFP_KERNEL);
|
|
|
|
if (!sysnames) {
|
|
|
|
seq_release(inode, file);
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
|
|
|
refcount_set(&sysnames->usage, 1);
|
|
|
|
m = file->private_data;
|
|
|
|
m->private = sysnames;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Handle writes to /proc/fs/afs/sysname to set the @sys substitution.
|
|
|
|
*/
|
|
|
|
static ssize_t afs_proc_sysname_write(struct file *file,
|
|
|
|
const char __user *buf,
|
|
|
|
size_t size, loff_t *_pos)
|
|
|
|
{
|
|
|
|
struct afs_sysnames *sysnames;
|
|
|
|
struct seq_file *m = file->private_data;
|
|
|
|
char *kbuf = NULL, *s, *p, *sub;
|
|
|
|
int ret, len;
|
|
|
|
|
|
|
|
sysnames = m->private;
|
|
|
|
if (!sysnames)
|
|
|
|
return -EINVAL;
|
|
|
|
if (sysnames->error)
|
|
|
|
return sysnames->error;
|
|
|
|
|
|
|
|
if (size >= PAGE_SIZE - 1) {
|
|
|
|
sysnames->error = -EINVAL;
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
if (size == 0)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
kbuf = memdup_user_nul(buf, size);
|
|
|
|
if (IS_ERR(kbuf))
|
|
|
|
return PTR_ERR(kbuf);
|
|
|
|
|
|
|
|
inode_lock(file_inode(file));
|
|
|
|
|
|
|
|
p = kbuf;
|
|
|
|
while ((s = strsep(&p, " \t\n"))) {
|
|
|
|
len = strlen(s);
|
|
|
|
if (len == 0)
|
|
|
|
continue;
|
|
|
|
ret = -ENAMETOOLONG;
|
|
|
|
if (len >= AFSNAMEMAX)
|
|
|
|
goto error;
|
|
|
|
|
|
|
|
if (len >= 4 &&
|
|
|
|
s[len - 4] == '@' &&
|
|
|
|
s[len - 3] == 's' &&
|
|
|
|
s[len - 2] == 'y' &&
|
|
|
|
s[len - 1] == 's')
|
|
|
|
/* Protect against recursion */
|
|
|
|
goto invalid;
|
|
|
|
|
|
|
|
if (s[0] == '.' &&
|
|
|
|
(len < 2 || (len == 2 && s[1] == '.')))
|
|
|
|
goto invalid;
|
|
|
|
|
|
|
|
if (memchr(s, '/', len))
|
|
|
|
goto invalid;
|
|
|
|
|
|
|
|
ret = -EFBIG;
|
|
|
|
if (sysnames->nr >= AFS_NR_SYSNAME)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
if (strcmp(s, afs_init_sysname) == 0) {
|
|
|
|
sub = (char *)afs_init_sysname;
|
|
|
|
} else {
|
|
|
|
ret = -ENOMEM;
|
|
|
|
sub = kmemdup(s, len + 1, GFP_KERNEL);
|
|
|
|
if (!sub)
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
sysnames->subs[sysnames->nr] = sub;
|
|
|
|
sysnames->nr++;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = size; /* consume everything, always */
|
|
|
|
out:
|
|
|
|
inode_unlock(file_inode(file));
|
|
|
|
kfree(kbuf);
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
invalid:
|
|
|
|
ret = -EINVAL;
|
|
|
|
error:
|
|
|
|
sysnames->error = ret;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int afs_proc_sysname_release(struct inode *inode, struct file *file)
|
|
|
|
{
|
|
|
|
struct afs_sysnames *sysnames, *kill = NULL;
|
|
|
|
struct seq_file *m = file->private_data;
|
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
|
|
|
|
sysnames = m->private;
|
|
|
|
if (sysnames) {
|
|
|
|
if (!sysnames->error) {
|
|
|
|
kill = sysnames;
|
|
|
|
if (sysnames->nr == 0) {
|
|
|
|
sysnames->subs[0] = sysnames->blank;
|
|
|
|
sysnames->nr++;
|
|
|
|
}
|
|
|
|
write_lock(&net->sysnames_lock);
|
|
|
|
kill = net->sysnames;
|
|
|
|
net->sysnames = sysnames;
|
|
|
|
write_unlock(&net->sysnames_lock);
|
|
|
|
}
|
|
|
|
afs_put_sysnames(kill);
|
|
|
|
}
|
|
|
|
|
|
|
|
return seq_release(inode, file);
|
|
|
|
}
|
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
static int afs_proc_sysname_show(struct seq_file *m, void *v)
|
|
|
|
{
|
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
struct afs_sysnames *sysnames = net->sysnames;
|
|
|
|
unsigned int i = (unsigned long)v - 1;
|
|
|
|
|
|
|
|
if (i < sysnames->nr)
|
|
|
|
seq_printf(m, "%s\n", sysnames->subs[i]);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-04-09 20:12:31 +00:00
|
|
|
static void *afs_proc_sysname_start(struct seq_file *m, loff_t *pos)
|
|
|
|
__acquires(&net->sysnames_lock)
|
|
|
|
{
|
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
struct afs_sysnames *names = net->sysnames;
|
|
|
|
|
|
|
|
read_lock(&net->sysnames_lock);
|
|
|
|
|
|
|
|
if (*pos >= names->nr)
|
|
|
|
return NULL;
|
|
|
|
return (void *)(unsigned long)(*pos + 1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void *afs_proc_sysname_next(struct seq_file *m, void *v, loff_t *pos)
|
|
|
|
{
|
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
struct afs_sysnames *names = net->sysnames;
|
|
|
|
|
|
|
|
*pos += 1;
|
|
|
|
if (*pos >= names->nr)
|
|
|
|
return NULL;
|
|
|
|
return (void *)(unsigned long)(*pos + 1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void afs_proc_sysname_stop(struct seq_file *m, void *v)
|
|
|
|
__releases(&net->sysnames_lock)
|
|
|
|
{
|
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
|
|
|
|
read_unlock(&net->sysnames_lock);
|
|
|
|
}
|
|
|
|
|
2018-05-18 10:46:14 +00:00
|
|
|
static const struct file_operations afs_proc_sysname_fops = {
|
|
|
|
.open = afs_proc_sysname_open,
|
|
|
|
.read = seq_read,
|
|
|
|
.llseek = seq_lseek,
|
|
|
|
.release = afs_proc_sysname_release,
|
|
|
|
.write = afs_proc_sysname_write,
|
|
|
|
};
|
|
|
|
|
2018-04-06 13:17:24 +00:00
|
|
|
/*
|
|
|
|
* Display general per-net namespace statistics
|
|
|
|
*/
|
|
|
|
static int afs_proc_stats_show(struct seq_file *m, void *v)
|
|
|
|
{
|
|
|
|
struct afs_net *net = afs_seq2net(m);
|
|
|
|
|
|
|
|
seq_puts(m, "kAFS statistics\n");
|
|
|
|
|
afs: Fix directory handling
AFS directories are structured blobs that are downloaded just like files
and then parsed by the lookup and readdir code and, as such, are currently
handled in the pagecache like any other file, with the entire directory
content being thrown away each time the directory changes.
However, since the blob is a known structure and since the data version
counter on a directory increases by exactly one for each change committed
to that directory, we can actually edit the directory locally rather than
fetching it from the server after each locally-induced change.
What we can't do, though, is mix data from the server and data from the
client since the server is technically at liberty to rearrange or compress
a directory if it sees fit, provided it updates the data version number
when it does so and breaks the callback (ie. sends a notification).
Further, lookup with lookup-ahead, readdir and, when it arrives, local
editing are likely want to scan the whole of a directory.
So directory handling needs to be improved to maintain the coherency of the
directory blob prior to permitting local directory editing.
To this end:
(1) If any directory page gets discarded, invalidate and reread the entire
directory.
(2) If readpage notes that if when it fetches a single page that the
version number has changed, the entire directory is flagged for
invalidation.
(3) Read as much of the directory in one go as we can.
Note that this removes local caching of directories in fscache for the
moment as we can't pass the pages to fscache_read_or_alloc_pages() since
page->lru is in use by the LRU.
Signed-off-by: David Howells <dhowells@redhat.com>
2018-04-06 13:17:25 +00:00
|
|
|
seq_printf(m, "dir-mgmt: look=%u reval=%u inval=%u relpg=%u\n",
|
2018-04-06 13:17:24 +00:00
|
|
|
atomic_read(&net->n_lookup),
|
|
|
|
atomic_read(&net->n_reval),
|
afs: Fix directory handling
AFS directories are structured blobs that are downloaded just like files
and then parsed by the lookup and readdir code and, as such, are currently
handled in the pagecache like any other file, with the entire directory
content being thrown away each time the directory changes.
However, since the blob is a known structure and since the data version
counter on a directory increases by exactly one for each change committed
to that directory, we can actually edit the directory locally rather than
fetching it from the server after each locally-induced change.
What we can't do, though, is mix data from the server and data from the
client since the server is technically at liberty to rearrange or compress
a directory if it sees fit, provided it updates the data version number
when it does so and breaks the callback (ie. sends a notification).
Further, lookup with lookup-ahead, readdir and, when it arrives, local
editing are likely want to scan the whole of a directory.
So directory handling needs to be improved to maintain the coherency of the
directory blob prior to permitting local directory editing.
To this end:
(1) If any directory page gets discarded, invalidate and reread the entire
directory.
(2) If readpage notes that if when it fetches a single page that the
version number has changed, the entire directory is flagged for
invalidation.
(3) Read as much of the directory in one go as we can.
Note that this removes local caching of directories in fscache for the
moment as we can't pass the pages to fscache_read_or_alloc_pages() since
page->lru is in use by the LRU.
Signed-off-by: David Howells <dhowells@redhat.com>
2018-04-06 13:17:25 +00:00
|
|
|
atomic_read(&net->n_inval),
|
|
|
|
atomic_read(&net->n_relpg));
|
2018-04-06 13:17:24 +00:00
|
|
|
|
|
|
|
seq_printf(m, "dir-data: rdpg=%u\n",
|
|
|
|
atomic_read(&net->n_read_dir));
|
2018-04-06 13:17:25 +00:00
|
|
|
|
|
|
|
seq_printf(m, "dir-edit: cr=%u rm=%u\n",
|
|
|
|
atomic_read(&net->n_dir_cr),
|
|
|
|
atomic_read(&net->n_dir_rm));
|
2018-04-06 13:17:26 +00:00
|
|
|
|
|
|
|
seq_printf(m, "file-rd : n=%u nb=%lu\n",
|
|
|
|
atomic_read(&net->n_fetches),
|
|
|
|
atomic_long_read(&net->n_fetch_bytes));
|
|
|
|
seq_printf(m, "file-wr : n=%u nb=%lu\n",
|
|
|
|
atomic_read(&net->n_stores),
|
|
|
|
atomic_long_read(&net->n_store_bytes));
|
2018-04-06 13:17:24 +00:00
|
|
|
return 0;
|
|
|
|
}
|
2018-05-18 10:46:14 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* initialise /proc/fs/afs/<cell>/
|
|
|
|
*/
|
|
|
|
int afs_proc_cell_setup(struct afs_net *net, struct afs_cell *cell)
|
|
|
|
{
|
|
|
|
struct proc_dir_entry *dir;
|
|
|
|
|
|
|
|
_enter("%p{%s},%p", cell, cell->name, net->proc_afs);
|
|
|
|
|
|
|
|
dir = proc_mkdir(cell->name, net->proc_afs);
|
|
|
|
if (!dir)
|
|
|
|
goto error_dir;
|
|
|
|
|
|
|
|
if (!proc_create_seq_data("vlservers", 0, dir,
|
|
|
|
&afs_proc_cell_vlservers_ops, cell))
|
|
|
|
goto error_tree;
|
|
|
|
if (!proc_create_seq_data("volumes", 0, dir,
|
|
|
|
&afs_proc_cell_volumes_ops, cell))
|
|
|
|
goto error_tree;
|
|
|
|
|
|
|
|
_leave(" = 0");
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
error_tree:
|
|
|
|
remove_proc_subtree(cell->name, net->proc_afs);
|
|
|
|
error_dir:
|
|
|
|
_leave(" = -ENOMEM");
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* remove /proc/fs/afs/<cell>/
|
|
|
|
*/
|
|
|
|
void afs_proc_cell_remove(struct afs_net *net, struct afs_cell *cell)
|
|
|
|
{
|
|
|
|
_enter("");
|
|
|
|
|
|
|
|
remove_proc_subtree(cell->name, net->proc_afs);
|
|
|
|
|
|
|
|
_leave("");
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* initialise the /proc/fs/afs/ directory
|
|
|
|
*/
|
|
|
|
int afs_proc_init(struct afs_net *net)
|
|
|
|
{
|
|
|
|
_enter("");
|
|
|
|
|
|
|
|
net->proc_afs = proc_mkdir("fs/afs", NULL);
|
|
|
|
if (!net->proc_afs)
|
|
|
|
goto error_dir;
|
|
|
|
|
|
|
|
if (!proc_create("cells", 0644, net->proc_afs, &afs_proc_cells_fops) ||
|
|
|
|
!proc_create("rootcell", 0644, net->proc_afs, &afs_proc_rootcell_fops) ||
|
|
|
|
!proc_create_seq("servers", 0644, net->proc_afs, &afs_proc_servers_ops) ||
|
|
|
|
!proc_create_single("stats", 0644, net->proc_afs, afs_proc_stats_show) ||
|
|
|
|
!proc_create("sysname", 0644, net->proc_afs, &afs_proc_sysname_fops))
|
|
|
|
goto error_tree;
|
|
|
|
|
|
|
|
_leave(" = 0");
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
error_tree:
|
|
|
|
proc_remove(net->proc_afs);
|
|
|
|
error_dir:
|
|
|
|
_leave(" = -ENOMEM");
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* clean up the /proc/fs/afs/ directory
|
|
|
|
*/
|
|
|
|
void afs_proc_cleanup(struct afs_net *net)
|
|
|
|
{
|
|
|
|
proc_remove(net->proc_afs);
|
|
|
|
net->proc_afs = NULL;
|
|
|
|
}
|