2005-06-06 13:40:32 +02:00
|
|
|
/* Implement entry point to select system call.
|
|
|
|
*
|
|
|
|
* The entry points into this file are
|
2005-06-17 15:41:12 +02:00
|
|
|
* do_select: perform the SELECT system call
|
2012-02-13 16:28:04 +01:00
|
|
|
* select_callback: notify select system of possible fd operation
|
endpoint-aware conversion of servers.
'who', indicating caller number in pm and fs and some other servers, has
been removed in favour of 'who_e' (endpoint) and 'who_p' (proc nr.).
In both PM and FS, isokendpt() convert endpoints to process slot
numbers, returning OK if it was a valid and consistent endpoint number.
okendpt() does the same but panic()s if it doesn't succeed. (In PM,
this is pm_isok..)
pm and fs keep their own records of process endpoints in their proc tables,
which are needed to make kernel calls about those processes.
message field names have changed.
fs drivers are endpoints.
fs now doesn't try to get out of driver deadlock, as the protocol isn't
supposed to let that happen any more. (A warning is printed if ELOCKED
is detected though.)
fproc[].fp_task (indicating which driver the process is suspended on)
became an int.
PM and FS now get endpoint numbers of initial boot processes from the
kernel. These happen to be the same as the old proc numbers, to let
user processes reach them with the old numbers, but FS and PM don't know
that. All new processes after INIT, even after the generation number
wraps around, get endpoint numbers with generation 1 and higher, so
the first instances of the boot processes are the only processes ever
to have endpoint numbers in the old proc number range.
More return code checks of sys_* functions have been added.
IS has become endpoint-aware. Ditched the 'text' and 'data' fields
in the kernel dump (which show locations, not sizes, so aren't terribly
useful) in favour of the endpoint number. Proc number is still visible.
Some other dumps (e.g. dmap, rs) show endpoint numbers now too which got
the formatting changed.
PM reading segments using rw_seg() has changed - it uses other fields
in the message now instead of encoding the segment and process number and
fd in the fd field. For that it uses _read_pm() and _write_pm() which to
_taskcall()s directly in pm/misc.c.
PM now sys_exit()s itself on panic(), instead of sys_abort().
RS also talks in endpoints instead of process numbers.
2006-03-03 11:20:58 +01:00
|
|
|
* select_unsuspend_by_endpt: cancel a blocking select on exiting driver
|
2013-08-30 13:42:51 +02:00
|
|
|
*
|
|
|
|
* The select code uses minimal locking, so that the replies from character
|
|
|
|
* drivers can be processed without blocking. Filps are locked only for pipes.
|
|
|
|
* We make the assumption that any other structures and fields are safe to
|
|
|
|
* check (and possibly change) as long as we know that a process is blocked on
|
|
|
|
* a select(2) call, meaning that all involved filps are guaranteed to stay
|
|
|
|
* open until either we finish the select call, it the process gets interrupted
|
|
|
|
* by a signal.
|
2005-06-06 13:40:32 +02:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include "fs.h"
|
2013-01-25 18:42:36 +01:00
|
|
|
#include <sys/fcntl.h>
|
2005-06-17 15:41:12 +02:00
|
|
|
#include <sys/time.h>
|
|
|
|
#include <sys/select.h>
|
2012-04-16 11:04:32 +02:00
|
|
|
#include <sys/stat.h>
|
2005-06-17 15:41:12 +02:00
|
|
|
#include <minix/com.h>
|
2006-11-27 15:21:43 +01:00
|
|
|
#include <minix/u64.h>
|
2005-06-17 15:41:12 +02:00
|
|
|
#include <string.h>
|
2011-04-13 15:25:34 +02:00
|
|
|
#include <assert.h>
|
|
|
|
|
|
|
|
#include "file.h"
|
|
|
|
#include "vnode.h"
|
2005-06-17 15:41:12 +02:00
|
|
|
|
|
|
|
/* max. number of simultaneously pending select() calls */
|
|
|
|
#define MAXSELECTS 25
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
#define FROM_PROC 0
|
|
|
|
#define TO_PROC 1
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2012-03-25 20:25:53 +02:00
|
|
|
static struct selectentry {
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
struct fproc *requestor; /* slot is free iff this is NULL */
|
2011-04-13 15:25:34 +02:00
|
|
|
endpoint_t req_endpt;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
fd_set readfds, writefds, errorfds;
|
|
|
|
fd_set ready_readfds, ready_writefds, ready_errorfds;
|
|
|
|
fd_set *vir_readfds, *vir_writefds, *vir_errorfds;
|
|
|
|
struct filp *filps[OPEN_MAX];
|
|
|
|
int type[OPEN_MAX];
|
|
|
|
int nfds, nreadyfds;
|
2011-04-13 15:25:34 +02:00
|
|
|
int error;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
char block;
|
2013-08-30 13:42:51 +02:00
|
|
|
char starting;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
clock_t expiry;
|
|
|
|
timer_t timer; /* if expiry > 0 */
|
2005-06-17 15:41:12 +02:00
|
|
|
} selecttab[MAXSELECTS];
|
|
|
|
|
2013-08-30 13:42:51 +02:00
|
|
|
static int copy_fdsets(struct selectentry *se, int nfds, int direction);
|
2012-03-25 20:25:53 +02:00
|
|
|
static void filp_status(struct filp *fp, int status);
|
|
|
|
static int is_deferred(struct selectentry *se);
|
|
|
|
static void restart_proc(struct selectentry *se);
|
|
|
|
static void ops2tab(int ops, int fd, struct selectentry *e);
|
|
|
|
static int is_regular_file(struct filp *f);
|
|
|
|
static int is_pipe(struct filp *f);
|
|
|
|
static int is_supported_major(struct filp *f);
|
|
|
|
static void select_lock_filp(struct filp *f, int ops);
|
|
|
|
static int select_request_file(struct filp *f, int *ops, int block);
|
|
|
|
static int select_request_major(struct filp *f, int *ops, int block);
|
|
|
|
static int select_request_pipe(struct filp *f, int *ops, int block);
|
|
|
|
static void select_cancel_all(struct selectentry *e);
|
|
|
|
static void select_cancel_filp(struct filp *f);
|
|
|
|
static void select_return(struct selectentry *);
|
|
|
|
static void select_restart_filps(void);
|
|
|
|
static int tab2ops(int fd, struct selectentry *e);
|
|
|
|
static void wipe_select(struct selectentry *s);
|
|
|
|
|
|
|
|
static struct fdtype {
|
2012-02-13 16:28:04 +01:00
|
|
|
int (*select_request)(struct filp *, int *ops, int block);
|
2011-04-13 15:25:34 +02:00
|
|
|
int (*type_match)(struct filp *f);
|
2012-02-13 16:28:04 +01:00
|
|
|
} fdtypes[] = {
|
2011-04-13 15:25:34 +02:00
|
|
|
{ select_request_major, is_supported_major },
|
|
|
|
{ select_request_file, is_regular_file },
|
|
|
|
{ select_request_pipe, is_pipe },
|
2005-06-17 15:41:12 +02:00
|
|
|
};
|
2006-06-07 16:41:47 +02:00
|
|
|
#define SEL_FDS (sizeof(fdtypes) / sizeof(fdtypes[0]))
|
2012-03-25 20:25:53 +02:00
|
|
|
static int select_majors[] = { /* List of majors that support selecting on */
|
2011-04-13 15:25:34 +02:00
|
|
|
TTY_MAJOR,
|
|
|
|
INET_MAJOR,
|
|
|
|
UDS_MAJOR,
|
|
|
|
LOG_MAJOR,
|
|
|
|
};
|
|
|
|
#define SEL_MAJORS (sizeof(select_majors) / sizeof(select_majors[0]))
|
2005-06-17 15:41:12 +02:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
/*===========================================================================*
|
2012-04-13 14:50:38 +02:00
|
|
|
* do_select *
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
*===========================================================================*/
|
2013-04-12 18:41:23 +02:00
|
|
|
int do_select(message *UNUSED(m_out))
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
{
|
|
|
|
/* Implement the select(nfds, readfds, writefds, errorfds, timeout) system
|
|
|
|
* call. First we copy the arguments and verify their sanity. Then we check
|
2013-08-30 13:42:51 +02:00
|
|
|
* whether there are file descriptors that satisfy the select call right off
|
|
|
|
* the bat. If so, or if there are no ready file descriptors but the process
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
* requested to return immediately, we return the result. Otherwise we set a
|
2012-02-13 16:28:04 +01:00
|
|
|
* timeout and wait for either the file descriptors to become ready or the
|
2013-08-30 13:42:51 +02:00
|
|
|
* timer to go off. If no timeout value was provided, we wait indefinitely.
|
|
|
|
*/
|
2010-03-22 21:43:06 +01:00
|
|
|
int r, nfds, do_timeout = 0, fd, s;
|
2013-08-30 13:42:51 +02:00
|
|
|
struct filp *f;
|
|
|
|
unsigned int type, ops;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
struct timeval timeout;
|
|
|
|
struct selectentry *se;
|
2012-04-13 14:50:38 +02:00
|
|
|
vir_bytes vtimeout;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2012-04-13 14:50:38 +02:00
|
|
|
nfds = job_m_in.SEL_NFDS;
|
|
|
|
vtimeout = (vir_bytes) job_m_in.SEL_TIMEOUT;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
/* Sane amount of file descriptors? */
|
|
|
|
if (nfds < 0 || nfds > OPEN_MAX) return(EINVAL);
|
|
|
|
|
|
|
|
/* Find a slot to store this select request */
|
|
|
|
for (s = 0; s < MAXSELECTS; s++)
|
|
|
|
if (selecttab[s].requestor == NULL) /* Unused slot */
|
|
|
|
break;
|
|
|
|
if (s >= MAXSELECTS) return(ENOSPC);
|
|
|
|
|
|
|
|
se = &selecttab[s];
|
2011-04-13 15:25:34 +02:00
|
|
|
wipe_select(se); /* Clear results of previous usage */
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
se->requestor = fp;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
se->req_endpt = who_e;
|
2012-04-13 14:50:38 +02:00
|
|
|
se->vir_readfds = (fd_set *) job_m_in.SEL_READFDS;
|
|
|
|
se->vir_writefds = (fd_set *) job_m_in.SEL_WRITEFDS;
|
|
|
|
se->vir_errorfds = (fd_set *) job_m_in.SEL_ERRORFDS;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
/* Copy fdsets from the process */
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
if ((r = copy_fdsets(se, nfds, FROM_PROC)) != OK) {
|
|
|
|
se->requestor = NULL;
|
|
|
|
return(r);
|
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
/* Did the process set a timeout value? If so, retrieve it. */
|
2012-04-13 14:50:38 +02:00
|
|
|
if (vtimeout != 0) {
|
2012-02-13 16:28:04 +01:00
|
|
|
do_timeout = 1;
|
2012-06-16 19:29:37 +02:00
|
|
|
r = sys_vircopy(who_e, (vir_bytes) vtimeout, SELF,
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
(vir_bytes) &timeout, sizeof(timeout));
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
if (r != OK) {
|
|
|
|
se->requestor = NULL;
|
|
|
|
return(r);
|
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/* No nonsense in the timeval */
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
if (do_timeout && (timeout.tv_sec < 0 || timeout.tv_usec < 0)) {
|
|
|
|
se->requestor = NULL;
|
2011-04-13 15:25:34 +02:00
|
|
|
return(EINVAL);
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
/* If there is no timeout, we block forever. Otherwise, we block up to the
|
2012-02-13 16:28:04 +01:00
|
|
|
* specified time interval.
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
if (!do_timeout) /* No timeout value set */
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
se->block = 1;
|
|
|
|
else if (do_timeout && (timeout.tv_sec > 0 || timeout.tv_usec > 0))
|
2012-02-13 16:28:04 +01:00
|
|
|
se->block = 1;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
else /* timeout set as (0,0) - this effects a poll */
|
2012-02-13 16:28:04 +01:00
|
|
|
se->block = 0;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
se->expiry = 0; /* no timer set (yet) */
|
|
|
|
|
2013-08-30 13:42:51 +02:00
|
|
|
/* We are going to lock filps, and that means that while locking a second
|
|
|
|
* filp, we might already get the results for the first one. In that case,
|
|
|
|
* the incoming results must not cause the select call to finish prematurely.
|
|
|
|
*/
|
|
|
|
se->starting = TRUE;
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Verify that file descriptors are okay to select on */
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
for (fd = 0; fd < nfds; fd++) {
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Because the select() interface implicitly includes file descriptors
|
|
|
|
* you might not want to select on, we have to figure out whether we're
|
|
|
|
* interested in them. Typically, these file descriptors include fd's
|
|
|
|
* inherited from the parent proc and file descriptors that have been
|
|
|
|
* close()d, but had a lower fd than one in the current set.
|
|
|
|
*/
|
2012-02-13 16:28:04 +01:00
|
|
|
if (!(ops = tab2ops(fd, se)))
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
continue; /* No operations set; nothing to do for this fd */
|
|
|
|
|
|
|
|
/* Get filp belonging to this fd */
|
2012-02-13 16:28:04 +01:00
|
|
|
f = se->filps[fd] = get_filp(fd, VNODE_READ);
|
2011-04-13 15:25:34 +02:00
|
|
|
if (f == NULL) {
|
2012-02-13 16:28:04 +01:00
|
|
|
if (err_code == EBADF)
|
2011-04-13 15:25:34 +02:00
|
|
|
r = err_code;
|
|
|
|
else /* File descriptor is 'ready' to return EIO */
|
|
|
|
r = EINTR;
|
|
|
|
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
se->requestor = NULL;
|
2011-04-13 15:25:34 +02:00
|
|
|
return(r);
|
2012-02-13 16:28:04 +01:00
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Check file types. According to POSIX 2008:
|
|
|
|
* "The pselect() and select() functions shall support regular files,
|
|
|
|
* terminal and pseudo-terminal devices, FIFOs, pipes, and sockets. The
|
|
|
|
* behavior of pselect() and select() on file descriptors that refer to
|
|
|
|
* other types of file is unspecified."
|
|
|
|
*
|
|
|
|
* In our case, terminal and pseudo-terminal devices are handled by the
|
|
|
|
* TTY major and sockets by either INET major (socket type AF_INET) or
|
|
|
|
* PFS major (socket type AF_UNIX). PFS acts as an FS when it handles
|
|
|
|
* pipes and as a driver when it handles sockets. Additionally, we
|
|
|
|
* support select on the LOG major to handle kernel logging, which is
|
|
|
|
* beyond the POSIX spec. */
|
|
|
|
|
|
|
|
se->type[fd] = -1;
|
|
|
|
for (type = 0; type < SEL_FDS; type++) {
|
|
|
|
if (fdtypes[type].type_match(f)) {
|
|
|
|
se->type[fd] = type;
|
|
|
|
se->nfds = fd+1;
|
|
|
|
se->filps[fd]->filp_selectors++;
|
|
|
|
break;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
|
|
|
}
|
2012-02-13 16:28:04 +01:00
|
|
|
unlock_filp(f);
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
if (se->type[fd] == -1) { /* Type not found */
|
|
|
|
se->requestor = NULL;
|
2010-10-08 14:50:52 +02:00
|
|
|
return(EBADF);
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Check all file descriptors in the set whether one is 'ready' now */
|
|
|
|
for (fd = 0; fd < nfds; fd++) {
|
|
|
|
/* Again, check for involuntarily selected fd's */
|
2012-02-13 16:28:04 +01:00
|
|
|
if (!(ops = tab2ops(fd, se)))
|
2011-04-13 15:25:34 +02:00
|
|
|
continue; /* No operations set; nothing to do for this fd */
|
|
|
|
|
2012-02-13 16:28:04 +01:00
|
|
|
/* Test filp for select operations if not already done so. e.g.,
|
2011-04-13 15:25:34 +02:00
|
|
|
* processes sharing a filp and both doing a select on that filp. */
|
|
|
|
f = se->filps[fd];
|
|
|
|
if ((f->filp_select_ops & ops) != ops) {
|
2011-06-09 16:09:13 +02:00
|
|
|
int wantops;
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
wantops = (f->filp_select_ops |= ops);
|
2013-08-30 13:42:51 +02:00
|
|
|
type = se->type[fd];
|
|
|
|
select_lock_filp(f, wantops);
|
|
|
|
r = fdtypes[type].select_request(f, &wantops, se->block);
|
|
|
|
unlock_filp(f);
|
|
|
|
if (r != OK && r != SUSPEND) {
|
|
|
|
se->error = r;
|
|
|
|
se->block = 0; /* Stop blocking to return asap */
|
2012-02-20 14:16:58 +01:00
|
|
|
break; /* Error or bogus return code; abort */
|
2013-08-30 13:42:51 +02:00
|
|
|
}
|
2012-02-13 16:28:04 +01:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
/* The select request above might have turned on/off some
|
|
|
|
* operations because they were 'ready' or not meaningful.
|
|
|
|
* Either way, we might have a result and we need to store them
|
|
|
|
* in the select table entry. */
|
|
|
|
if (wantops & ops) ops2tab(wantops, fd, se);
|
2012-02-13 16:28:04 +01:00
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
|
|
|
|
2013-08-30 13:42:51 +02:00
|
|
|
/* At this point there won't be any blocking calls anymore. */
|
|
|
|
se->starting = FALSE;
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if ((se->nreadyfds > 0 || !se->block) && !is_deferred(se)) {
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
/* fd's were found that were ready to go right away, and/or
|
|
|
|
* we were instructed not to block at all. Must return
|
|
|
|
* immediately.
|
|
|
|
*/
|
|
|
|
r = copy_fdsets(se, se->nfds, TO_PROC);
|
|
|
|
select_cancel_all(se);
|
VFS: make all IPC asynchronous
By decoupling synchronous drivers from VFS, we are a big step closer to
supporting driver crashes under all circumstances. That is, VFS can't
become stuck on IPC with a synchronous driver (e.g., INET) and can
recover from crashing block drivers during open/close/ioctl or during
communication with an FS.
In order to maintain serialized communication with a synchronous driver,
the communication is wrapped by a mutex on a per driver basis (not major
numbers as there can be multiple majors with identical endpoints). Majors
that share a driver endpoint point to a single mutex object.
In order to support crashes from block drivers, the file reopen tactic
had to be changed; first reopen files associated with the crashed
driver, then send the new driver endpoint to FSes. This solves a
deadlock between the FS and the block driver;
- VFS would send REQ_NEW_DRIVER to an FS, but he FS only receives it
after retrying the current request to the newly started driver.
- The block driver would refuse the retried request until all files
had been reopened.
- VFS would reopen files only after getting a reply from the initial
REQ_NEW_DRIVER.
When a character special driver crashes, all associated files have to
be marked invalid and closed (or reopened if flagged as such). However,
they can only be closed if a thread holds exclusive access to it. To
obtain exclusive access, the worker thread (which handles the new driver
endpoint event from DS) schedules a new job to garbage collect invalid
files. This way, we can signal the worker thread that was talking to the
crashed driver and will release exclusive access to a file associated
with the crashed driver and prevent the garbage collecting worker thread
from dead locking on that file.
Also, when a character special driver crashes, RS will unmap the driver
and remap it upon restart. During unmapping, associated files are marked
invalid instead of waiting for an endpoint up event from DS, as that
event might come later than new read/write/select requests and thus
cause confusion in the freshly started driver.
When locking a filp, the usage counters are no longer checked. The usage
counter can legally go down to zero during filp invalidation while there
are locks pending.
DS events are handled by a separate worker thread instead of the main
thread as reopening files could lead to another crash and a stuck thread.
An additional worker thread is then necessary to unlock it.
Finally, with everything asynchronous a race condition in do_select
surfaced. A select entry was only marked in use after succesfully sending
initial select requests to drivers and having to wait. When multiple
select() calls were handled there was opportunity that these entries
were overwritten. This had as effect that some select results were
ignored (and select() remained blocking instead if returning) or do_select
tried to access filps that were not present (because thrown away by
secondary select()). This bug manifested itself with sendrecs, but was
very hard to reproduce. However, it became awfully easy to trigger with
asynsends only.
2012-08-28 16:06:51 +02:00
|
|
|
se->requestor = NULL;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (r != OK)
|
|
|
|
return(r);
|
|
|
|
else if (se->error != OK)
|
|
|
|
return(se->error);
|
|
|
|
|
|
|
|
return(se->nreadyfds);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
2012-02-13 16:28:04 +01:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
/* Convert timeval to ticks and set the timer. If it fails, undo
|
|
|
|
* all, return error.
|
|
|
|
*/
|
|
|
|
if (do_timeout) {
|
|
|
|
int ticks;
|
|
|
|
/* Open Group:
|
|
|
|
* "If the requested timeout interval requires a finer
|
|
|
|
* granularity than the implementation supports, the
|
|
|
|
* actual timeout interval shall be rounded up to the next
|
|
|
|
* supported value."
|
|
|
|
*/
|
|
|
|
#define USECPERSEC 1000000
|
|
|
|
while(timeout.tv_usec >= USECPERSEC) {
|
|
|
|
/* this is to avoid overflow with *system_hz below */
|
|
|
|
timeout.tv_usec -= USECPERSEC;
|
|
|
|
timeout.tv_sec++;
|
|
|
|
}
|
|
|
|
ticks = timeout.tv_sec * system_hz +
|
|
|
|
(timeout.tv_usec * system_hz + USECPERSEC-1) / USECPERSEC;
|
|
|
|
se->expiry = ticks;
|
2010-07-09 14:58:18 +02:00
|
|
|
set_timer(&se->timer, ticks, select_timeout_check, s);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/* process now blocked */
|
|
|
|
suspend(FP_BLOCKED_ON_SELECT);
|
|
|
|
return(SUSPEND);
|
|
|
|
}
|
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2011-04-13 15:25:34 +02:00
|
|
|
* is_deferred *
|
2005-06-17 15:41:12 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int is_deferred(struct selectentry *se)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Find out whether this select has pending initial replies */
|
|
|
|
|
|
|
|
int fd;
|
|
|
|
struct filp *f;
|
|
|
|
|
2013-08-30 13:42:51 +02:00
|
|
|
/* The select call must have finished its initialization at all. */
|
|
|
|
if (se->starting) return(TRUE);
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
for (fd = 0; fd < se->nfds; fd++) {
|
|
|
|
if ((f = se->filps[fd]) == NULL) continue;
|
|
|
|
if (f->filp_select_flags & (FSF_UPDATE|FSF_BUSY)) return(TRUE);
|
|
|
|
}
|
|
|
|
|
|
|
|
return(FALSE);
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2011-04-13 15:25:34 +02:00
|
|
|
* is_regular_file *
|
2005-06-17 15:41:12 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int is_regular_file(struct filp *f)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2012-04-25 14:44:42 +02:00
|
|
|
return(f && f->filp_vno && S_ISREG(f->filp_vno->v_mode));
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* is_pipe *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int is_pipe(struct filp *f)
|
2011-04-13 15:25:34 +02:00
|
|
|
{
|
|
|
|
/* Recognize either anonymous pipe or named pipe (FIFO) */
|
2012-04-16 11:04:32 +02:00
|
|
|
return(f && f->filp_vno && S_ISFIFO(f->filp_vno->v_mode));
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2012-04-13 14:50:38 +02:00
|
|
|
* is_supported_major *
|
2005-06-17 15:41:12 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int is_supported_major(struct filp *f)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* See if this filp is a handle on a character device on which we support
|
|
|
|
* select(). This function MUST NOT block its calling thread. The given filp
|
|
|
|
* may or may not be locked.
|
|
|
|
*/
|
2012-04-02 17:16:44 +02:00
|
|
|
unsigned int m;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (!(f && f->filp_vno)) return(FALSE);
|
2012-04-25 14:44:42 +02:00
|
|
|
if (!S_ISCHR(f->filp_vno->v_mode)) return(FALSE);
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2012-02-13 16:28:04 +01:00
|
|
|
for (m = 0; m < SEL_MAJORS; m++)
|
|
|
|
if (major(f->filp_vno->v_sdev) == select_majors[m])
|
|
|
|
return(TRUE);
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
return(FALSE);
|
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2008-02-22 16:46:59 +01:00
|
|
|
/*===========================================================================*
|
2013-08-30 13:33:56 +02:00
|
|
|
* select_request_major *
|
2008-02-22 16:46:59 +01:00
|
|
|
*===========================================================================*/
|
2013-08-30 13:33:56 +02:00
|
|
|
static int select_request_major(struct filp *f, int *ops, int block)
|
2008-02-22 16:46:59 +01:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Check readiness status on a supported character device. Unless suitable
|
|
|
|
* results are available right now, this will only initiate the polling
|
|
|
|
* process, causing result processing to be deferred. This function MUST NOT
|
|
|
|
* block its calling thread. The given filp may or may not be locked.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int r, rops, major;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
struct dmap *dp;
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2013-08-30 13:33:56 +02:00
|
|
|
major = major(f->filp_vno->v_sdev);
|
|
|
|
if (major < 0 || major >= NR_DEVICES) return(ENXIO);
|
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
rops = *ops;
|
2011-04-13 15:25:34 +02:00
|
|
|
|
2012-02-20 14:16:58 +01:00
|
|
|
/* By default, nothing to do */
|
|
|
|
*ops = 0;
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (!block && (f->filp_select_flags & FSF_BLOCKED)) {
|
|
|
|
/* This filp is blocked waiting for a reply, but we don't want to
|
|
|
|
* block ourselves. Unless we're awaiting the initial reply, these
|
|
|
|
* operations won't be ready */
|
|
|
|
if (!(f->filp_select_flags & FSF_BUSY)) {
|
|
|
|
if ((rops & SEL_RD) && (f->filp_select_flags & FSF_RD_BLOCK))
|
|
|
|
rops &= ~SEL_RD;
|
|
|
|
if ((rops & SEL_WR) && (f->filp_select_flags & FSF_WR_BLOCK))
|
|
|
|
rops &= ~SEL_WR;
|
|
|
|
if ((rops & SEL_ERR) && (f->filp_select_flags & FSF_ERR_BLOCK))
|
|
|
|
rops &= ~SEL_ERR;
|
2012-02-20 14:16:58 +01:00
|
|
|
if (!(rops & (SEL_RD|SEL_WR|SEL_ERR)))
|
2012-02-17 14:36:57 +01:00
|
|
|
return(OK);
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
f->filp_select_flags |= FSF_UPDATE;
|
|
|
|
if (block) {
|
|
|
|
rops |= SEL_NOTIFY;
|
2011-04-13 15:25:34 +02:00
|
|
|
if (rops & SEL_RD) f->filp_select_flags |= FSF_RD_BLOCK;
|
|
|
|
if (rops & SEL_WR) f->filp_select_flags |= FSF_WR_BLOCK;
|
|
|
|
if (rops & SEL_ERR) f->filp_select_flags |= FSF_ERR_BLOCK;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
if (f->filp_select_flags & FSF_BUSY)
|
2012-02-17 14:36:57 +01:00
|
|
|
return(SUSPEND);
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
dp = &dmap[major];
|
2013-08-25 00:26:38 +02:00
|
|
|
if (dp->dmap_sel_busy)
|
2012-02-17 14:36:57 +01:00
|
|
|
return(SUSPEND);
|
2008-02-22 16:46:59 +01:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
f->filp_select_flags &= ~FSF_UPDATE;
|
2013-08-30 13:33:56 +02:00
|
|
|
r = dev_select(f->filp_vno->v_sdev, rops);
|
|
|
|
if (r != OK)
|
2012-02-17 14:36:57 +01:00
|
|
|
return(r);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2013-08-25 00:26:38 +02:00
|
|
|
dp->dmap_sel_busy = TRUE;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
dp->dmap_sel_filp = f;
|
|
|
|
f->filp_select_flags |= FSF_BUSY;
|
|
|
|
|
2012-02-17 14:36:57 +01:00
|
|
|
return(SUSPEND);
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2011-04-13 15:25:34 +02:00
|
|
|
* select_request_file *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int select_request_file(struct filp *UNUSED(f), int *UNUSED(ops),
|
2012-02-13 16:28:04 +01:00
|
|
|
int UNUSED(block))
|
2011-04-13 15:25:34 +02:00
|
|
|
{
|
|
|
|
/* Files are always ready, so output *ops is input *ops */
|
2012-02-17 14:36:57 +01:00
|
|
|
return(OK);
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* select_request_pipe *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int select_request_pipe(struct filp *f, int *ops, int block)
|
2011-04-13 15:25:34 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Check readiness status on a pipe. The given filp is locked. This function
|
|
|
|
* may block its calling thread if necessary.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int orig_ops, r = 0, err;
|
|
|
|
|
|
|
|
orig_ops = *ops;
|
|
|
|
|
|
|
|
if ((*ops & (SEL_RD|SEL_ERR))) {
|
2012-12-11 20:46:09 +01:00
|
|
|
/* Check if we can read 1 byte */
|
2013-02-25 12:36:29 +01:00
|
|
|
err = pipe_check(f, READING, f->filp_flags & ~O_NONBLOCK, 1,
|
2013-01-25 18:42:36 +01:00
|
|
|
1 /* Check only */);
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
if (err != SUSPEND)
|
|
|
|
r |= SEL_RD;
|
|
|
|
if (err < 0 && err != SUSPEND)
|
|
|
|
r |= SEL_ERR;
|
|
|
|
if (err == SUSPEND && !(f->filp_mode & R_BIT)) {
|
|
|
|
/* A "meaningless" read select, therefore ready
|
|
|
|
* for reading and no error set. */
|
2012-02-13 16:28:04 +01:00
|
|
|
r |= SEL_RD;
|
2011-04-13 15:25:34 +02:00
|
|
|
r &= ~SEL_ERR;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if ((*ops & (SEL_WR|SEL_ERR))) {
|
2012-12-11 20:46:09 +01:00
|
|
|
/* Check if we can write 1 byte */
|
2013-02-25 12:36:29 +01:00
|
|
|
err = pipe_check(f, WRITING, f->filp_flags & ~O_NONBLOCK, 1,
|
2013-01-25 18:42:36 +01:00
|
|
|
1 /* Check only */);
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
if (err != SUSPEND)
|
|
|
|
r |= SEL_WR;
|
|
|
|
if (err < 0 && err != SUSPEND)
|
|
|
|
r |= SEL_ERR;
|
|
|
|
if (err == SUSPEND && !(f->filp_mode & W_BIT)) {
|
|
|
|
/* A "meaningless" write select, therefore ready
|
|
|
|
for writing and no error set. */
|
2012-02-13 16:28:04 +01:00
|
|
|
r |= SEL_WR;
|
2011-04-13 15:25:34 +02:00
|
|
|
r &= ~SEL_ERR;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Some options we collected might not be requested. */
|
|
|
|
*ops = r & orig_ops;
|
|
|
|
|
|
|
|
if (!*ops && block)
|
|
|
|
f->filp_pipe_select_ops |= orig_ops;
|
|
|
|
|
2012-02-17 14:36:57 +01:00
|
|
|
return(OK);
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-09-22 23:17:22 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* tab2ops *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int tab2ops(int fd, struct selectentry *e)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
int ops = 0;
|
|
|
|
if (FD_ISSET(fd, &e->readfds)) ops |= SEL_RD;
|
|
|
|
if (FD_ISSET(fd, &e->writefds)) ops |= SEL_WR;
|
|
|
|
if (FD_ISSET(fd, &e->errorfds)) ops |= SEL_ERR;
|
2012-02-13 16:28:04 +01:00
|
|
|
|
|
|
|
return(ops);
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-09-22 23:17:22 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* ops2tab *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void ops2tab(int ops, int fd, struct selectentry *e)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
if ((ops & SEL_RD) && e->vir_readfds && FD_ISSET(fd, &e->readfds) &&
|
|
|
|
!FD_ISSET(fd, &e->ready_readfds)) {
|
|
|
|
FD_SET(fd, &e->ready_readfds);
|
|
|
|
e->nreadyfds++;
|
|
|
|
}
|
|
|
|
|
|
|
|
if ((ops & SEL_WR) && e->vir_writefds && FD_ISSET(fd, &e->writefds) &&
|
|
|
|
!FD_ISSET(fd, &e->ready_writefds)) {
|
|
|
|
FD_SET(fd, &e->ready_writefds);
|
|
|
|
e->nreadyfds++;
|
|
|
|
}
|
|
|
|
|
|
|
|
if ((ops & SEL_ERR) && e->vir_errorfds && FD_ISSET(fd, &e->errorfds) &&
|
|
|
|
!FD_ISSET(fd, &e->ready_errorfds)) {
|
|
|
|
FD_SET(fd, &e->ready_errorfds);
|
|
|
|
e->nreadyfds++;
|
|
|
|
}
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-09-22 23:17:22 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* copy_fdsets *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int copy_fdsets(struct selectentry *se, int nfds, int direction)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Copy FD sets from or to the user process calling select(2). This function
|
|
|
|
* MUST NOT block the calling thread.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int r;
|
|
|
|
size_t fd_setsize;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
endpoint_t src_e, dst_e;
|
|
|
|
fd_set *src_fds, *dst_fds;
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (nfds < 0 || nfds > OPEN_MAX)
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("select copy_fdsets: nfds wrong: %d", nfds);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
/* Only copy back as many bits as the user expects. */
|
2011-04-27 15:00:52 +02:00
|
|
|
fd_setsize = (size_t) (howmany(nfds, __NFDBITS) * sizeof(__fd_mask));
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
/* Set source and destination endpoints */
|
|
|
|
src_e = (direction == FROM_PROC) ? se->req_endpt : SELF;
|
|
|
|
dst_e = (direction == FROM_PROC) ? SELF : se->req_endpt;
|
|
|
|
|
|
|
|
/* read set */
|
|
|
|
src_fds = (direction == FROM_PROC) ? se->vir_readfds : &se->ready_readfds;
|
|
|
|
dst_fds = (direction == FROM_PROC) ? &se->readfds : se->vir_readfds;
|
|
|
|
if (se->vir_readfds) {
|
2012-06-16 19:29:37 +02:00
|
|
|
r = sys_vircopy(src_e, (vir_bytes) src_fds, dst_e,
|
2011-04-13 15:25:34 +02:00
|
|
|
(vir_bytes) dst_fds, fd_setsize);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
if (r != OK) return(r);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* write set */
|
|
|
|
src_fds = (direction == FROM_PROC) ? se->vir_writefds : &se->ready_writefds;
|
|
|
|
dst_fds = (direction == FROM_PROC) ? &se->writefds : se->vir_writefds;
|
|
|
|
if (se->vir_writefds) {
|
2012-06-16 19:29:37 +02:00
|
|
|
r = sys_vircopy(src_e, (vir_bytes) src_fds, dst_e,
|
2011-04-13 15:25:34 +02:00
|
|
|
(vir_bytes) dst_fds, fd_setsize);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
if (r != OK) return(r);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* error set */
|
|
|
|
src_fds = (direction == FROM_PROC) ? se->vir_errorfds : &se->ready_errorfds;
|
|
|
|
dst_fds = (direction == FROM_PROC) ? &se->errorfds : se->vir_errorfds;
|
|
|
|
if (se->vir_errorfds) {
|
2012-06-16 19:29:37 +02:00
|
|
|
r = sys_vircopy(src_e, (vir_bytes) src_fds, dst_e,
|
2011-04-13 15:25:34 +02:00
|
|
|
(vir_bytes) dst_fds, fd_setsize);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
if (r != OK) return(r);
|
|
|
|
}
|
|
|
|
|
|
|
|
return(OK);
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
2005-06-06 13:40:32 +02:00
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2005-09-22 23:17:22 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* select_cancel_all *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void select_cancel_all(struct selectentry *se)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Cancel select, possibly on success. Decrease select usage and cancel timer.
|
|
|
|
* This function MUST NOT block its calling thread.
|
|
|
|
*/
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
int fd;
|
|
|
|
struct filp *f;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
for (fd = 0; fd < se->nfds; fd++) {
|
|
|
|
if ((f = se->filps[fd]) == NULL) continue;
|
|
|
|
se->filps[fd] = NULL;
|
|
|
|
select_cancel_filp(f);
|
|
|
|
}
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (se->expiry > 0) {
|
2012-02-13 16:28:04 +01:00
|
|
|
cancel_timer(&se->timer);
|
2011-04-13 15:25:34 +02:00
|
|
|
se->expiry = 0;
|
|
|
|
}
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
se->requestor = NULL;
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
|
|
|
|
2005-10-20 21:39:32 +02:00
|
|
|
/*===========================================================================*
|
2011-04-13 15:25:34 +02:00
|
|
|
* select_cancel_filp *
|
2005-10-20 21:39:32 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void select_cancel_filp(struct filp *f)
|
2005-10-20 21:39:32 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Reduce the number of select users of this filp. This function MUST NOT block
|
|
|
|
* its calling thread.
|
|
|
|
*/
|
2013-08-25 00:26:38 +02:00
|
|
|
dev_t major;
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
assert(f);
|
2013-08-25 00:26:38 +02:00
|
|
|
assert(f->filp_selectors > 0);
|
|
|
|
assert(f->filp_count > 0);
|
2012-02-13 16:28:04 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
f->filp_selectors--;
|
2012-02-13 16:28:04 +01:00
|
|
|
if (f->filp_selectors == 0) {
|
2011-04-13 15:25:34 +02:00
|
|
|
/* No one selecting on this filp anymore, forget about select state */
|
|
|
|
f->filp_select_ops = 0;
|
|
|
|
f->filp_select_flags = 0;
|
|
|
|
f->filp_pipe_select_ops = 0;
|
2013-08-25 00:26:38 +02:00
|
|
|
|
|
|
|
/* If this filp is the subject of an ongoing select query to a
|
|
|
|
* character device, mark the query as stale, so that this filp will
|
|
|
|
* not be checked when the result arrives.
|
|
|
|
*/
|
|
|
|
if (is_supported_major(f)) {
|
|
|
|
major = major(f->filp_vno->v_sdev);
|
|
|
|
if (dmap[major].dmap_sel_busy &&
|
|
|
|
dmap[major].dmap_sel_filp == f)
|
|
|
|
dmap[major].dmap_sel_filp = NULL; /* leave _busy set */
|
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
2005-10-20 21:39:32 +02:00
|
|
|
}
|
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2011-04-13 15:25:34 +02:00
|
|
|
* select_return *
|
2005-06-17 15:41:12 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void select_return(struct selectentry *se)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Return the results of a select call to the user process and revive the
|
|
|
|
* process. This function MUST NOT block its calling thread.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int r, r1;
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
assert(!is_deferred(se)); /* Not done yet, first wait for async reply */
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
select_cancel_all(se);
|
2012-02-13 16:28:04 +01:00
|
|
|
|
|
|
|
r1 = copy_fdsets(se, se->nfds, TO_PROC);
|
2011-04-13 15:25:34 +02:00
|
|
|
if (r1 != OK)
|
2012-02-13 16:28:04 +01:00
|
|
|
r = r1;
|
2011-04-13 15:25:34 +02:00
|
|
|
else if (se->error != OK)
|
2012-02-13 16:28:04 +01:00
|
|
|
r = se->error;
|
2011-04-13 15:25:34 +02:00
|
|
|
else
|
2012-02-13 16:28:04 +01:00
|
|
|
r = se->nreadyfds;
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
revive(se->req_endpt, r);
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2011-04-13 15:25:34 +02:00
|
|
|
* select_callback *
|
2005-06-17 15:41:12 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
void select_callback(struct filp *f, int status)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* The status of a filp has changed, with the given ready operations or error.
|
|
|
|
* This function is currently called only for pipes, and holds the lock to
|
|
|
|
* the filp.
|
|
|
|
*/
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
filp_status(f, status);
|
2005-06-06 13:40:32 +02:00
|
|
|
}
|
2005-07-27 15:08:52 +02:00
|
|
|
|
2005-07-22 20:28:32 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* init_select *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
void init_select(void)
|
2005-07-22 20:28:32 +02:00
|
|
|
{
|
2011-04-13 15:25:34 +02:00
|
|
|
int s;
|
2005-07-22 20:28:32 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
for (s = 0; s < MAXSELECTS; s++)
|
|
|
|
init_timer(&selecttab[s].timer);
|
2005-07-22 20:28:32 +02:00
|
|
|
}
|
2005-06-06 13:40:32 +02:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2005-09-11 18:45:46 +02:00
|
|
|
* select_forget *
|
2005-06-17 15:41:12 +02:00
|
|
|
*===========================================================================*/
|
2013-08-25 00:26:38 +02:00
|
|
|
void select_forget(void)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2013-08-25 00:26:38 +02:00
|
|
|
/* The calling thread's associated process is expected to be unpaused, due to
|
2013-08-30 13:42:51 +02:00
|
|
|
* a signal that is supposed to interrupt the current system call. Totally
|
|
|
|
* forget about the select(). This function may block its calling thread if
|
|
|
|
* necessary (but it doesn't).
|
2013-08-25 00:26:38 +02:00
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int slot;
|
|
|
|
struct selectentry *se;
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
for (slot = 0; slot < MAXSELECTS; slot++) {
|
|
|
|
se = &selecttab[slot];
|
2013-08-25 00:26:38 +02:00
|
|
|
if (se->requestor == fp)
|
2011-04-13 15:25:34 +02:00
|
|
|
break;
|
|
|
|
}
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (slot >= MAXSELECTS) return; /* Entry not found */
|
2005-06-17 15:41:12 +02:00
|
|
|
|
2013-08-30 13:42:51 +02:00
|
|
|
assert(se->starting == FALSE);
|
|
|
|
|
2013-08-25 00:26:38 +02:00
|
|
|
/* Do NOT test on is_deferred here. We can safely cancel ongoing queries. */
|
2011-04-13 15:25:34 +02:00
|
|
|
select_cancel_all(se);
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-06-17 15:41:12 +02:00
|
|
|
/*===========================================================================*
|
2005-09-11 18:45:46 +02:00
|
|
|
* select_timeout_check *
|
2005-06-17 15:41:12 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
void select_timeout_check(timer_t *timer)
|
2005-06-17 15:41:12 +02:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* An alarm has gone off for one of the select queries. This function MUST NOT
|
|
|
|
* block its calling thread.
|
|
|
|
*/
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
int s;
|
|
|
|
struct selectentry *se;
|
2005-06-17 15:41:12 +02:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
s = tmr_arg(timer)->ta_int;
|
2011-04-13 15:25:34 +02:00
|
|
|
if (s < 0 || s >= MAXSELECTS) return; /* Entry does not exist */
|
2012-02-13 16:28:04 +01:00
|
|
|
|
|
|
|
se = &selecttab[s];
|
2011-04-13 15:25:34 +02:00
|
|
|
if (se->requestor == NULL) return;
|
|
|
|
if (se->expiry <= 0) return; /* Strange, did we even ask for a timeout? */
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
se->expiry = 0;
|
2011-04-13 15:25:34 +02:00
|
|
|
if (is_deferred(se)) return; /* Wait for initial replies to DEV_SELECT */
|
|
|
|
select_return(se);
|
2005-06-17 15:41:12 +02:00
|
|
|
}
|
2005-10-20 21:39:32 +02:00
|
|
|
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2005-10-20 21:39:32 +02:00
|
|
|
/*===========================================================================*
|
endpoint-aware conversion of servers.
'who', indicating caller number in pm and fs and some other servers, has
been removed in favour of 'who_e' (endpoint) and 'who_p' (proc nr.).
In both PM and FS, isokendpt() convert endpoints to process slot
numbers, returning OK if it was a valid and consistent endpoint number.
okendpt() does the same but panic()s if it doesn't succeed. (In PM,
this is pm_isok..)
pm and fs keep their own records of process endpoints in their proc tables,
which are needed to make kernel calls about those processes.
message field names have changed.
fs drivers are endpoints.
fs now doesn't try to get out of driver deadlock, as the protocol isn't
supposed to let that happen any more. (A warning is printed if ELOCKED
is detected though.)
fproc[].fp_task (indicating which driver the process is suspended on)
became an int.
PM and FS now get endpoint numbers of initial boot processes from the
kernel. These happen to be the same as the old proc numbers, to let
user processes reach them with the old numbers, but FS and PM don't know
that. All new processes after INIT, even after the generation number
wraps around, get endpoint numbers with generation 1 and higher, so
the first instances of the boot processes are the only processes ever
to have endpoint numbers in the old proc number range.
More return code checks of sys_* functions have been added.
IS has become endpoint-aware. Ditched the 'text' and 'data' fields
in the kernel dump (which show locations, not sizes, so aren't terribly
useful) in favour of the endpoint number. Proc number is still visible.
Some other dumps (e.g. dmap, rs) show endpoint numbers now too which got
the formatting changed.
PM reading segments using rw_seg() has changed - it uses other fields
in the message now instead of encoding the segment and process number and
fd in the fd field. For that it uses _read_pm() and _write_pm() which to
_taskcall()s directly in pm/misc.c.
PM now sys_exit()s itself on panic(), instead of sys_abort().
RS also talks in endpoints instead of process numbers.
2006-03-03 11:20:58 +01:00
|
|
|
* select_unsuspend_by_endpt *
|
2005-10-20 21:39:32 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
void select_unsuspend_by_endpt(endpoint_t proc_e)
|
2005-10-20 21:39:32 +02:00
|
|
|
{
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Revive blocked processes when a driver has disappeared */
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
int fd, s, major;
|
|
|
|
struct selectentry *se;
|
|
|
|
struct filp *f;
|
|
|
|
|
|
|
|
for (s = 0; s < MAXSELECTS; s++) {
|
2012-02-13 16:28:04 +01:00
|
|
|
int wakehim = 0;
|
|
|
|
se = &selecttab[s];
|
2011-04-13 15:25:34 +02:00
|
|
|
if (se->requestor == NULL) continue;
|
2012-02-13 16:28:04 +01:00
|
|
|
if (se->requestor->fp_endpoint == proc_e) {
|
|
|
|
assert(se->requestor->fp_flags & FP_EXITING);
|
|
|
|
select_cancel_all(se);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
for (fd = 0; fd < se->nfds; fd++) {
|
2012-02-13 16:28:04 +01:00
|
|
|
if ((f = se->filps[fd]) == NULL || f->filp_vno == NULL)
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
continue;
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
major = major(f->filp_vno->v_sdev);
|
|
|
|
if (dmap_driver_match(proc_e, major)) {
|
|
|
|
se->filps[fd] = NULL;
|
|
|
|
se->error = EINTR;
|
|
|
|
select_cancel_filp(f);
|
|
|
|
wakehim = 1;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
2005-10-20 21:39:32 +02:00
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
|
|
|
|
if (wakehim && !is_deferred(se))
|
|
|
|
select_return(se);
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
}
|
2005-10-20 21:39:32 +02:00
|
|
|
}
|
|
|
|
|
2008-02-22 16:46:59 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
* select_reply1 *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
void select_reply1(driver_e, minor, status)
|
2011-04-13 15:25:34 +02:00
|
|
|
endpoint_t driver_e;
|
|
|
|
int minor;
|
|
|
|
int status;
|
2008-02-22 16:46:59 +01:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Handle the initial reply to DEV_SELECT request. This function MUST NOT
|
|
|
|
* block its calling thread.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int major;
|
|
|
|
dev_t dev;
|
|
|
|
struct filp *f;
|
|
|
|
struct dmap *dp;
|
|
|
|
struct vnode *vp;
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Figure out which device is replying */
|
2012-02-13 16:28:04 +01:00
|
|
|
if ((dp = get_dmap(driver_e)) == NULL) return;
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
major = dp-dmap;
|
|
|
|
dev = makedev(major, minor);
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Get filp belonging to character special file */
|
2013-08-25 00:26:38 +02:00
|
|
|
if (!dp->dmap_sel_busy) {
|
2011-04-13 15:25:34 +02:00
|
|
|
printf("VFS (%s:%d): major %d was not expecting a DEV_SELECT reply\n",
|
|
|
|
__FILE__, __LINE__, major);
|
|
|
|
return;
|
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2013-08-25 00:26:38 +02:00
|
|
|
/* The select filp may have been set to NULL if the requestor has been
|
|
|
|
* unpaused in the meantime. In that case, we ignore the result, but we do
|
|
|
|
* look for other filps to restart later.
|
|
|
|
*/
|
|
|
|
if ((f = dp->dmap_sel_filp) != NULL) {
|
2011-07-15 16:11:34 +02:00
|
|
|
/* Find vnode and check we got a reply from the device we expected */
|
|
|
|
vp = f->filp_vno;
|
|
|
|
assert(vp != NULL);
|
2012-04-25 14:44:42 +02:00
|
|
|
assert(S_ISCHR(vp->v_mode));
|
2011-07-15 16:11:34 +02:00
|
|
|
if (vp->v_sdev != dev) {
|
2013-08-25 00:26:38 +02:00
|
|
|
/* This should never happen. The driver may be misbehaving.
|
|
|
|
* For now we assume that the reply we want will arrive later..
|
|
|
|
*/
|
2011-07-15 16:11:34 +02:00
|
|
|
printf("VFS (%s:%d): expected reply from dev %d not %d\n",
|
2011-09-08 15:57:03 +02:00
|
|
|
__FILE__, __LINE__, vp->v_sdev, dev);
|
2011-07-15 16:11:34 +02:00
|
|
|
return;
|
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/* No longer waiting for a reply from this device */
|
2013-08-25 00:26:38 +02:00
|
|
|
dp->dmap_sel_busy = FALSE;
|
2011-04-13 15:25:34 +02:00
|
|
|
dp->dmap_sel_filp = NULL;
|
|
|
|
|
2013-08-25 00:26:38 +02:00
|
|
|
/* Process the select result only if the filp is valid. */
|
|
|
|
if (f != NULL) {
|
|
|
|
assert(f->filp_count >= 1);
|
|
|
|
assert(f->filp_select_flags & FSF_BUSY);
|
|
|
|
|
2012-02-13 16:28:04 +01:00
|
|
|
f->filp_select_flags &= ~FSF_BUSY;
|
|
|
|
|
|
|
|
/* The select call is done now, except when
|
|
|
|
* - another process started a select on the same filp with possibly a
|
|
|
|
* different set of operations.
|
|
|
|
* - a process does a select on the same filp but using different file
|
|
|
|
* descriptors.
|
|
|
|
* - the select has a timeout. Upon receiving this reply the operations
|
|
|
|
* might not be ready yet, so we want to wait for that to ultimately
|
|
|
|
* happen.
|
|
|
|
* Therefore we need to keep remembering what the operations are.
|
|
|
|
*/
|
|
|
|
if (!(f->filp_select_flags & (FSF_UPDATE|FSF_BLOCKED)))
|
|
|
|
f->filp_select_ops = 0; /* done selecting */
|
|
|
|
else if (!(f->filp_select_flags & FSF_UPDATE))
|
|
|
|
/* there may be operations pending */
|
|
|
|
f->filp_select_ops &= ~status;
|
|
|
|
|
2012-02-17 14:36:57 +01:00
|
|
|
/* Record new filp status */
|
2012-02-13 16:28:04 +01:00
|
|
|
if (!(status == 0 && (f->filp_select_flags & FSF_BLOCKED))) {
|
|
|
|
if (status > 0) { /* operations ready */
|
|
|
|
if (status & SEL_RD)
|
|
|
|
f->filp_select_flags &= ~FSF_RD_BLOCK;
|
|
|
|
if (status & SEL_WR)
|
|
|
|
f->filp_select_flags &= ~FSF_WR_BLOCK;
|
|
|
|
if (status & SEL_ERR)
|
|
|
|
f->filp_select_flags &= ~FSF_ERR_BLOCK;
|
|
|
|
} else if (status < 0) { /* error */
|
|
|
|
/* Always unblock upon error */
|
|
|
|
f->filp_select_flags &= ~FSF_BLOCKED;
|
|
|
|
}
|
|
|
|
}
|
2012-02-17 14:36:57 +01:00
|
|
|
|
|
|
|
filp_status(f, status); /* Tell filp owners about the results */
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
select_restart_filps();
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* select_reply2 *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
void select_reply2(driver_e, minor, status)
|
2011-04-13 15:25:34 +02:00
|
|
|
endpoint_t driver_e;
|
|
|
|
int minor;
|
|
|
|
int status;
|
2008-02-22 16:46:59 +01:00
|
|
|
{
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Handle secondary reply to DEV_SELECT request. A secondary reply occurs when
|
2013-08-30 13:42:51 +02:00
|
|
|
* the select request is 'blocking' until an operation becomes ready. This
|
|
|
|
* function MUST NOT block its calling thread.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int major, slot, fd;
|
|
|
|
dev_t dev;
|
|
|
|
struct filp *f;
|
|
|
|
struct dmap *dp;
|
|
|
|
struct vnode *vp;
|
|
|
|
struct selectentry *se;
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (status == 0) {
|
2012-02-13 16:28:04 +01:00
|
|
|
printf("VFS (%s:%d): weird status (%d) to report\n",
|
|
|
|
__FILE__, __LINE__, status);
|
|
|
|
return;
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Figure out which device is replying */
|
|
|
|
if ((dp = get_dmap(driver_e)) == NULL) {
|
|
|
|
printf("VFS (%s:%d): endpoint %d is not a known driver endpoint\n",
|
|
|
|
__FILE__, __LINE__, driver_e);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
major = dp-dmap;
|
|
|
|
dev = makedev(major, minor);
|
|
|
|
|
|
|
|
/* Find all file descriptors selecting for this device */
|
|
|
|
for (slot = 0; slot < MAXSELECTS; slot++) {
|
2012-02-13 16:28:04 +01:00
|
|
|
se = &selecttab[slot];
|
2011-04-13 15:25:34 +02:00
|
|
|
if (se->requestor == NULL) continue; /* empty slot */
|
2012-02-13 16:28:04 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
for (fd = 0; fd < se->nfds; fd++) {
|
|
|
|
if ((f = se->filps[fd]) == NULL) continue;
|
|
|
|
if ((vp = f->filp_vno) == NULL) continue;
|
2012-04-25 14:44:42 +02:00
|
|
|
if (!S_ISCHR(vp->v_mode)) continue;
|
2011-04-13 15:25:34 +02:00
|
|
|
if (vp->v_sdev != dev) continue;
|
2012-02-13 16:28:04 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
if (status > 0) { /* Operations ready */
|
|
|
|
/* Clear the replied bits from the request
|
|
|
|
* mask unless FSF_UPDATE is set.
|
|
|
|
*/
|
2012-02-13 16:28:04 +01:00
|
|
|
if (!(f->filp_select_flags & FSF_UPDATE))
|
2011-04-13 15:25:34 +02:00
|
|
|
f->filp_select_ops &= ~status;
|
|
|
|
if (status & SEL_RD)
|
|
|
|
f->filp_select_flags &= ~FSF_RD_BLOCK;
|
|
|
|
if (status & SEL_WR)
|
|
|
|
f->filp_select_flags &= ~FSF_WR_BLOCK;
|
|
|
|
if (status & SEL_ERR)
|
|
|
|
f->filp_select_flags &= ~FSF_ERR_BLOCK;
|
|
|
|
|
|
|
|
ops2tab(status, fd, se);
|
|
|
|
} else {
|
2012-02-13 16:28:04 +01:00
|
|
|
f->filp_select_flags &= ~FSF_BLOCKED;
|
2011-04-13 15:25:34 +02:00
|
|
|
ops2tab(SEL_RD|SEL_WR|SEL_ERR, fd, se);
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
if (se->nreadyfds > 0) restart_proc(se);
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
select_restart_filps();
|
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* select_restart_filps *
|
|
|
|
*===========================================================================*/
|
2013-08-30 13:42:51 +02:00
|
|
|
static void select_restart_filps(void)
|
2008-02-22 16:46:59 +01:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* We got a result from a character driver, and now we need to check if we can
|
|
|
|
* restart deferred polling operations. This function MUST NOT block its
|
|
|
|
* calling thread.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int fd, slot;
|
|
|
|
struct filp *f;
|
|
|
|
struct selectentry *se;
|
|
|
|
|
|
|
|
/* Locate filps that can be restarted */
|
|
|
|
for (slot = 0; slot < MAXSELECTS; slot++) {
|
|
|
|
se = &selecttab[slot];
|
|
|
|
if (se->requestor == NULL) continue; /* empty slot */
|
|
|
|
|
|
|
|
/* Only 'deferred' processes are eligible to restart */
|
|
|
|
if (!is_deferred(se)) continue;
|
|
|
|
|
|
|
|
/* Find filps that are not waiting for a reply, but have an updated
|
2012-02-13 16:28:04 +01:00
|
|
|
* status (i.e., another select on the same filp with possibly a
|
2011-04-13 15:25:34 +02:00
|
|
|
* different set of operations is to be done), and thus requires the
|
|
|
|
* select request to be sent again).
|
|
|
|
*/
|
|
|
|
for (fd = 0; fd < se->nfds; fd++) {
|
2011-06-09 16:09:13 +02:00
|
|
|
int r, wantops, ops;
|
2011-04-13 15:25:34 +02:00
|
|
|
if ((f = se->filps[fd]) == NULL) continue;
|
|
|
|
if (f->filp_select_flags & FSF_BUSY) /* Still waiting for */
|
|
|
|
continue; /* initial reply */
|
|
|
|
if (!(f->filp_select_flags & FSF_UPDATE)) /* Must be in */
|
|
|
|
continue; /* 'update' state */
|
|
|
|
|
2013-08-30 13:42:51 +02:00
|
|
|
/* This function is suitable only for character devices. In
|
|
|
|
* particular, checking pipes the same way would introduce a
|
|
|
|
* serious locking problem.
|
|
|
|
*/
|
|
|
|
assert(is_supported_major(f));
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
wantops = ops = f->filp_select_ops;
|
2013-08-30 13:42:51 +02:00
|
|
|
r = select_request_major(f, &wantops, se->block);
|
|
|
|
if (r != OK && r != SUSPEND) {
|
|
|
|
se->error = r;
|
|
|
|
se->block = 0; /* Stop blocking to return asap */
|
|
|
|
restart_proc(se);
|
2012-02-20 14:16:58 +01:00
|
|
|
break; /* Error or bogus return code; abort */
|
2013-08-30 13:42:51 +02:00
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
if (wantops & ops) ops2tab(wantops, fd, se);
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* filp_status *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void filp_status(f, status)
|
2011-04-13 15:25:34 +02:00
|
|
|
struct filp *f;
|
2008-02-22 16:46:59 +01:00
|
|
|
int status;
|
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Tell processes that need to know about the status of this filp. This
|
|
|
|
* function MUST NOT block its calling thread.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
int fd, slot;
|
|
|
|
struct selectentry *se;
|
|
|
|
|
|
|
|
for (slot = 0; slot < MAXSELECTS; slot++) {
|
|
|
|
se = &selecttab[slot];
|
|
|
|
if (se->requestor == NULL) continue; /* empty slot */
|
|
|
|
|
|
|
|
for (fd = 0; fd < se->nfds; fd++) {
|
|
|
|
if (se->filps[fd] != f) continue;
|
|
|
|
if (status < 0)
|
|
|
|
ops2tab(SEL_RD|SEL_WR|SEL_ERR, fd, se);
|
2012-02-13 16:28:04 +01:00
|
|
|
else
|
2011-04-13 15:25:34 +02:00
|
|
|
ops2tab(status, fd, se);
|
|
|
|
restart_proc(se);
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
2011-04-13 15:25:34 +02:00
|
|
|
}
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
|
|
|
|
2011-04-13 15:25:34 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* restart_proc *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void restart_proc(se)
|
2011-04-13 15:25:34 +02:00
|
|
|
struct selectentry *se;
|
2008-02-22 16:46:59 +01:00
|
|
|
{
|
2011-04-13 15:25:34 +02:00
|
|
|
/* Tell process about select results (if any) unless there are still results
|
2013-08-30 13:42:51 +02:00
|
|
|
* pending. This function MUST NOT block its calling thread.
|
|
|
|
*/
|
2011-04-13 15:25:34 +02:00
|
|
|
|
2012-02-13 16:28:04 +01:00
|
|
|
if ((se->nreadyfds > 0 || !se->block) && !is_deferred(se))
|
2011-04-13 15:25:34 +02:00
|
|
|
select_return(se);
|
2008-02-22 16:46:59 +01:00
|
|
|
}
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* wipe_select *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void wipe_select(struct selectentry *se)
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
{
|
|
|
|
se->nfds = 0;
|
|
|
|
se->nreadyfds = 0;
|
2011-04-13 15:25:34 +02:00
|
|
|
se->error = OK;
|
2012-02-13 16:28:04 +01:00
|
|
|
se->block = 0;
|
|
|
|
memset(se->filps, 0, sizeof(se->filps));
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
|
|
|
|
FD_ZERO(&se->readfds);
|
|
|
|
FD_ZERO(&se->writefds);
|
|
|
|
FD_ZERO(&se->errorfds);
|
|
|
|
FD_ZERO(&se->ready_readfds);
|
|
|
|
FD_ZERO(&se->ready_writefds);
|
|
|
|
FD_ZERO(&se->ready_errorfds);
|
|
|
|
}
|
|
|
|
|
2012-02-13 16:28:04 +01:00
|
|
|
/*===========================================================================*
|
2012-04-13 14:50:38 +02:00
|
|
|
* select_lock_filp *
|
2012-02-13 16:28:04 +01:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void select_lock_filp(struct filp *f, int ops)
|
2012-02-13 16:28:04 +01:00
|
|
|
{
|
2013-08-30 13:42:51 +02:00
|
|
|
/* Lock a filp and vnode based on which operations are requested. This function
|
|
|
|
* may block its calling thread, obviously.
|
|
|
|
*/
|
|
|
|
tll_access_t locktype;
|
2012-02-13 16:28:04 +01:00
|
|
|
|
|
|
|
locktype = VNODE_READ; /* By default */
|
|
|
|
|
|
|
|
if (ops & (SEL_WR|SEL_ERR))
|
|
|
|
/* Selecting for error or writing requires exclusive access */
|
|
|
|
locktype = VNODE_WRITE;
|
|
|
|
|
|
|
|
lock_filp(f, locktype);
|
|
|
|
}
|