Age | Commit message (Collapse) | Author |
|
and recover for the client case (or terminate with EINTR if to many retries),
and in the server case, if we cant send due to f.x network troubles its up to
the client to retry not the server.
(server not responding messages are logged in another place though).
discussed with deraadt@
|
|
Replace nfs_kqinit() wich just calls lockinit with
RWLOCK_INITALIZER. Assorted cleanup.
ok tedu@
"reads good" art@
|
|
multiple defines all over;
ok tedu@
|
|
There's no need to extern stuff thats declared in the same file.
ok tedu@
|
|
Not doing so can lead to clients missing out if the file is for
example removed on the server and the client is doing a 'tail -f' on it.
If it returns ESTALE, mark the file deleted and proceed to handling the
next entry.
ok tedu@,art@
|
|
ok pedro@
|
|
ok pedro@
|
|
|
|
|
|
tends to .nfs silly files lying around during high filesystem activity.
whatever bug it was trying to fix, it made things worse.
|
|
crash when unmounting nfs volumes, okay thib@, krw@ and mickey@
|
|
effectively been a no-op for quite some time now,
without promise for future usage.
ok pedro@
Testing by krw@ (earlier diff)
and Johan Mson Lindman (tybollt@solace.miun.se)
|
|
|
|
Replace the pointer aerobics used to construct the
namecache hash with a more saner approach since the
former could lead to a null deref (PR5305).
Also make sure that the current buf is bigenough
before caching the current entry.
comments&ok pedro@
|
|
should never be referenced outside the context of the process to which
this stack belongs unless we do the PHOLD/PRELE dance. Loads of code
doesn't follow the rules here. Instead of trying to track down all
offenders and fix this hairy situation, it makes much more sense
to not swap kernel stacks.
From art@, tested by many some time ago.
|
|
nfs_subs.c so it gets pulled in for NFSSERVER only
kernels.
ok deraadt@,krw@
|
|
out of bounds.
ok pedro@
|
|
|
|
in the case where NFSERR_TRYLATER is received from the server.
Adapted from NetBSD.
ok pedro@, tedu@
|
|
with Nicholas Marriott <nicm__@ntlworld.com>, closes PR 5036
|
|
requested by and ok pedro
|
|
|
|
ok tedu, pedro
|
|
requested by deraadt@
|
|
- new sysctl vfs.nfs.privport to require NFS mount requests to be on
reserved ports when set to 1 (the default).
- mountd now automatically sets the sysctl depending on the -n flag.
- add mountd_flags to rc.conf to enable the -n flag at boot.
deraadt@ ok
|
|
|
|
without breaking into ddb. doubles the size of rwlock [1], but moving
forward this really helps. ok/tested pedro fgsch millert krw
[1 - next person to add a field to this struct gets whipped with a wet noodle]
|
|
used and will never be used this way in VFS
requested by and ok pedro, ok krw, biorn
|
|
to hold all the entries a directory has, we can't signal EOF.
Okay deraadt@ and miod@.
|
|
|
|
|
|
problem experienced by Han Boetes; fix with "nfs4" rick at snowhite
dot cis dot uoguelph dot ca. ok pedro@ tedu@
|
|
become NULL if the nfs_reply() -> nfs_receive() -> nfs_reconnect() datapath
fails. pedro@ ok "I think this is a good fix"
|
|
Inspiration from miod@, okay deraadt@. Tested on i386, macppc and amd64.
|
|
which duplicates work done by uvm_swap_init().
|
|
anymore. Testing by jolan@, thanks.
|
|
|
|
of panics and bugfixes. Access curproc directly, do not expect a process
pointer as an argument. Should fix many "process context required" bugs.
Incentive and okay millert@, okay marc@. Various testing, thanks.
|
|
when earlier merges were done. Fixes PR 4250. ok millert@ deraadt@
|
|
|
|
|
|
|
|
ok pedro@
|
|
belonging to a mount point if we want to skip all of them, okay art@ a
couple of days ago, commit it deraadt@
|
|
|
|
<mark@2ls4agd.net> on several archs
|
|
|
|
> fix preposterous time warnings in the nfs client; caused by false hits
> in the attribute cache
> based on original fix by pedro@, ok pedro@, tedu@; testing kettenis@
was backed out because too close to release
put back in now, since tree is unlocked. unfortunately it appears that even
after MANY MAILS ON THIS SUBJECT, NOONE HAS DONE THIS. WTF? Noone wants
to FINISH jobs anymore?
|
|
> fix preposterous time warnings in the nfs client; caused by false hits
> in the attribute cache
> based on original fix by pedro@, ok pedro@, tedu@; testing kettenis@
was backed out because too close to release
put back in now, since tree is unlocked. unfortunately it appears that even
after MANY MAILS ON THIS SUBJECT, NOONE HAS DONE THIS. WTF? Noone wants
to FINISH jobs anymore?
|
|
fix preposterous time warnings in the nfs client; caused by false hits
in the attribute cache
too close to release, save for immediately after unlock
|