2005-04-21 16:53:53 +02:00
|
|
|
/* This file handles advisory file locking as required by POSIX.
|
|
|
|
*
|
|
|
|
* The entry points into this file are
|
|
|
|
* lock_op: perform locking operations for FCNTL system call
|
|
|
|
* lock_revive: revive processes when a lock is released
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "fs.h"
|
|
|
|
#include <minix/com.h>
|
2006-11-27 15:21:43 +01:00
|
|
|
#include <minix/u64.h>
|
2005-04-21 16:53:53 +02:00
|
|
|
#include <fcntl.h>
|
|
|
|
#include <unistd.h>
|
|
|
|
#include "file.h"
|
|
|
|
#include "fproc.h"
|
|
|
|
#include "lock.h"
|
|
|
|
#include "param.h"
|
2006-10-25 15:40:36 +02:00
|
|
|
#include "vnode.h"
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* lock_op *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC int lock_op(f, req)
|
|
|
|
struct filp *f;
|
|
|
|
int req; /* either F_SETLK or F_SETLKW */
|
|
|
|
{
|
|
|
|
/* Perform the advisory locking required by POSIX. */
|
|
|
|
|
|
|
|
int r, ltype, i, conflict = 0, unlocking = 0;
|
|
|
|
mode_t mo;
|
|
|
|
off_t first, last;
|
|
|
|
struct flock flock;
|
|
|
|
vir_bytes user_flock;
|
|
|
|
struct file_lock *flp, *flp2, *empty;
|
|
|
|
|
|
|
|
/* Fetch the flock structure from user space. */
|
|
|
|
user_flock = (vir_bytes) m_in.name1;
|
2010-06-08 15:58:01 +02:00
|
|
|
r = sys_datacopy(who_e, (vir_bytes) user_flock, VFS_PROC_NR,
|
- 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) &flock, (phys_bytes) sizeof(flock));
|
2005-04-21 16:53:53 +02:00
|
|
|
if (r != OK) return(EINVAL);
|
|
|
|
|
|
|
|
/* Make some error checks. */
|
|
|
|
ltype = flock.l_type;
|
|
|
|
mo = f->filp_mode;
|
|
|
|
if (ltype != F_UNLCK && ltype != F_RDLCK && ltype != F_WRLCK) return(EINVAL);
|
|
|
|
if (req == F_GETLK && ltype == F_UNLCK) return(EINVAL);
|
2006-10-25 15:40:36 +02:00
|
|
|
if ( (f->filp_vno->v_mode & I_TYPE) != I_REGULAR) return(EINVAL);
|
2005-04-21 16:53:53 +02:00
|
|
|
if (req != F_GETLK && ltype == F_RDLCK && (mo & R_BIT) == 0) return(EBADF);
|
|
|
|
if (req != F_GETLK && ltype == F_WRLCK && (mo & W_BIT) == 0) return(EBADF);
|
|
|
|
|
|
|
|
/* Compute the first and last bytes in the lock region. */
|
|
|
|
switch (flock.l_whence) {
|
|
|
|
case SEEK_SET: first = 0; break;
|
2006-11-27 15:21:43 +01:00
|
|
|
case SEEK_CUR:
|
- 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 (ex64hi(f->filp_pos) != 0)
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("lock_op: position in file too high");
|
- 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
|
|
|
first = ex64lo(f->filp_pos);
|
|
|
|
break;
|
2006-10-25 15:40:36 +02:00
|
|
|
case SEEK_END: first = f->filp_vno->v_size; break;
|
2005-04-21 16:53:53 +02:00
|
|
|
default: return(EINVAL);
|
|
|
|
}
|
2010-04-28 13:54:22 +02:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
/* Check for overflow. */
|
|
|
|
if (((long)flock.l_start > 0) && ((first + flock.l_start) < first))
|
|
|
|
return(EINVAL);
|
|
|
|
if (((long)flock.l_start < 0) && ((first + flock.l_start) > first))
|
|
|
|
return(EINVAL);
|
|
|
|
first = first + flock.l_start;
|
|
|
|
last = first + flock.l_len - 1;
|
|
|
|
if (flock.l_len == 0) last = MAX_FILE_POS;
|
|
|
|
if (last < first) return(EINVAL);
|
|
|
|
|
|
|
|
/* Check if this region conflicts with any existing lock. */
|
2010-05-10 15:26:00 +02:00
|
|
|
empty = NULL;
|
2010-04-28 13:54:22 +02:00
|
|
|
for (flp = &file_lock[0]; flp < &file_lock[NR_LOCKS]; flp++) {
|
2005-04-21 16:53:53 +02:00
|
|
|
if (flp->lock_type == 0) {
|
2010-05-10 15:26:00 +02:00
|
|
|
if (empty == NULL) empty = flp;
|
2005-04-21 16:53:53 +02:00
|
|
|
continue; /* 0 means unused slot */
|
|
|
|
}
|
2006-10-25 15:40:36 +02:00
|
|
|
if (flp->lock_vnode != f->filp_vno) continue; /* different file */
|
2005-04-21 16:53:53 +02:00
|
|
|
if (last < flp->lock_first) continue; /* new one is in front */
|
|
|
|
if (first > flp->lock_last) continue; /* new one is afterwards */
|
|
|
|
if (ltype == F_RDLCK && flp->lock_type == F_RDLCK) continue;
|
|
|
|
if (ltype != F_UNLCK && flp->lock_pid == fp->fp_pid) continue;
|
|
|
|
|
|
|
|
/* There might be a conflict. Process it. */
|
|
|
|
conflict = 1;
|
|
|
|
if (req == F_GETLK) break;
|
|
|
|
|
|
|
|
/* If we are trying to set a lock, it just failed. */
|
|
|
|
if (ltype == F_RDLCK || ltype == F_WRLCK) {
|
|
|
|
if (req == F_SETLK) {
|
|
|
|
/* For F_SETLK, just report back failure. */
|
|
|
|
return(EAGAIN);
|
|
|
|
} else {
|
|
|
|
/* For F_SETLKW, suspend the process. */
|
2009-09-22 23:48:26 +02:00
|
|
|
suspend(FP_BLOCKED_ON_LOCK);
|
2005-04-21 16:53:53 +02:00
|
|
|
return(SUSPEND);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* We are clearing a lock and we found something that overlaps. */
|
|
|
|
unlocking = 1;
|
|
|
|
if (first <= flp->lock_first && last >= flp->lock_last) {
|
|
|
|
flp->lock_type = 0; /* mark slot as unused */
|
|
|
|
nr_locks--; /* number of locks is now 1 less */
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Part of a locked region has been unlocked. */
|
|
|
|
if (first <= flp->lock_first) {
|
|
|
|
flp->lock_first = last + 1;
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (last >= flp->lock_last) {
|
|
|
|
flp->lock_last = first - 1;
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Bad luck. A lock has been split in two by unlocking the middle. */
|
|
|
|
if (nr_locks == NR_LOCKS) return(ENOLCK);
|
|
|
|
for (i = 0; i < NR_LOCKS; i++)
|
|
|
|
if (file_lock[i].lock_type == 0) break;
|
|
|
|
flp2 = &file_lock[i];
|
|
|
|
flp2->lock_type = flp->lock_type;
|
|
|
|
flp2->lock_pid = flp->lock_pid;
|
2006-10-25 15:40:36 +02:00
|
|
|
flp2->lock_vnode = flp->lock_vnode;
|
2005-04-21 16:53:53 +02:00
|
|
|
flp2->lock_first = last + 1;
|
|
|
|
flp2->lock_last = flp->lock_last;
|
|
|
|
flp->lock_last = first - 1;
|
|
|
|
nr_locks++;
|
|
|
|
}
|
|
|
|
if (unlocking) lock_revive();
|
|
|
|
|
|
|
|
if (req == F_GETLK) {
|
|
|
|
if (conflict) {
|
|
|
|
/* GETLK and conflict. Report on the conflicting lock. */
|
|
|
|
flock.l_type = flp->lock_type;
|
|
|
|
flock.l_whence = SEEK_SET;
|
|
|
|
flock.l_start = flp->lock_first;
|
|
|
|
flock.l_len = flp->lock_last - flp->lock_first + 1;
|
|
|
|
flock.l_pid = flp->lock_pid;
|
|
|
|
|
|
|
|
} else {
|
|
|
|
/* It is GETLK and there is no conflict. */
|
|
|
|
flock.l_type = F_UNLCK;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Copy the flock structure back to the caller. */
|
2010-06-08 15:58:01 +02:00
|
|
|
r = sys_datacopy(VFS_PROC_NR, (vir_bytes) &flock,
|
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
|
|
|
who_e, (vir_bytes) user_flock, (phys_bytes) sizeof(flock));
|
2005-04-21 16:53:53 +02:00
|
|
|
return(r);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ltype == F_UNLCK) return(OK); /* unlocked a region with no locks */
|
|
|
|
|
|
|
|
/* There is no conflict. If space exists, store new lock in the table. */
|
2010-05-10 15:26:00 +02:00
|
|
|
if (empty == NULL) return(ENOLCK); /* table full */
|
2005-04-21 16:53:53 +02:00
|
|
|
empty->lock_type = ltype;
|
|
|
|
empty->lock_pid = fp->fp_pid;
|
2006-10-25 15:40:36 +02:00
|
|
|
empty->lock_vnode = f->filp_vno;
|
2005-04-21 16:53:53 +02:00
|
|
|
empty->lock_first = first;
|
|
|
|
empty->lock_last = last;
|
|
|
|
nr_locks++;
|
|
|
|
return(OK);
|
|
|
|
}
|
|
|
|
|
- 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-04-21 16:53:53 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* lock_revive *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC void lock_revive()
|
|
|
|
{
|
|
|
|
/* Go find all the processes that are waiting for any kind of lock and
|
|
|
|
* revive them all. The ones that are still blocked will block again when
|
|
|
|
* they run. The others will complete. This strategy is a space-time
|
|
|
|
* tradeoff. Figuring out exactly which ones to unblock now would take
|
|
|
|
* extra code, and the only thing it would win would be some performance in
|
|
|
|
* extremely rare circumstances (namely, that somebody actually used
|
|
|
|
* locking).
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct fproc *fptr;
|
|
|
|
|
2010-04-28 13:54:22 +02:00
|
|
|
for (fptr = &fproc[0]; fptr < &fproc[NR_PROCS]; fptr++){
|
2006-03-15 16:34:12 +01:00
|
|
|
if(fptr->fp_pid == PID_FREE) continue;
|
2009-09-22 23:48:26 +02:00
|
|
|
if (fptr->fp_blocked_on == FP_BLOCKED_ON_LOCK) {
|
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
|
|
|
revive(fptr->fp_endpoint, 0);
|
2005-04-21 16:53:53 +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
|
|
|
|