branches: 1.1.4; 1.1.6; 1.1.10;
Explain what's here.

One more option for the opt_ file.

Add the initial module(9) infrastructure

Clean up after the import auto-generate.

At least now it doesn't cause config(1) any problems.

Resolve conflicts

add missing attribute

branches: 1.2.2; 1.2.4;
Define filesystem attributes with vfs dependency.

branches: 1.1.1;
Initial revision

branches: 1.1.1; 1.1.4; 1.1.6; 1.1.10;
The script for preparing an import of this nfs code.

More changes for creds, mutex, etc.

branches: 1.1.1;
Initial revision

Don't use legacy VM types.

branches: 1.6.2; 1.6.4;
s/implicitely/implicitly/

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.4.14; 1.4.16;
More clean-up of #includes

Resolve conflicts

branches: 1.2.4; 1.2.6; 1.2.10; 1.2.12; 1.2.16;
Fix typo ("then" instead of "than")

branches: 1.1.1;
Initial revision

s/ony/only/

s/derefernce/dereference/ in comment.

More clean-up of #includes

branches: 1.1.1;
Initial revision

branches: 1.2.2; 1.2.4; 1.2.18;
More clean-up of #includes

branches: 1.1.1;
Initial revision

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.2.52;
Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

branches: 1.1.1;
Initial revision

branches: 1.1.2; 1.1.4; 1.1.18;
Add the initial module(9) infrastructure

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

branches: 1.1.1;
Initial revision

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

More clean-up of #includes

branches: 1.1.1;
Initial revision

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

branches: 1.1.1;
Initial revision

Fix various typos, mainly in comments.

Fix various typos in comments.

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.3.2;
fix misplaced or missing "e" in words with "ment" ending (argument, implement,
increment, decrement, alignment), in comments, documentation, log messages.

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

branches: 1.1.1;
Initial revision

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

Resolve conflicts

branches: 1.2.2; 1.2.4;
src is too big these days to tolerate superfluous apostrophes. It's
"its", people!

branches: 1.1.1;
Initial revision

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

branches: 1.1.1;
Initial revision

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.2.14; 1.2.16;
Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

branches: 1.1.1;
Initial revision

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

Resolve conflicts

branches: 1.2.4; 1.2.6; 1.2.10; 1.2.12; 1.2.16;
kill sprintf.

branches: 1.1.1;
Initial revision

Update to FreeBSD revision 308975 ( approx 2016-11-18 07:30 UTC)

If I'm going to try to get this working, I should at least start with
the most recent code available.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10; 1.1.1.1.12; 1.1.1.1.16;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

More clean-up of #includes

branches: 1.1.1;
Initial revision

Adapt code for our location of the nfs headers, and some updates for
differences in kernel options(4) handling

More clean-up of #includes

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

Clean up some #includes

branches: 1.1.1;
Initial revision

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

branches: 1.1.1;
Initial revision

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.6.52;
Clean up some #includes

Resolve conflicts

branches: 1.4.2;
Introduce m_set_rcvif and m_reset_rcvif

The API is used to set (or reset) a received interface of a mbuf.
They are counterpart of m_get_rcvif, which will come in another
commit, hide internal of rcvif operation, and reduce the diff of
the upcoming change.

No functional change.

invalidate input mbuf as soon as it is consumed by the mbuf chain
to avoid a double free later.

fix mbuf leak; this is not being compiled yet.
Reported by:
http://www.m00nbsd.net/ae123a9bae03f7dde5c6d654412daf5a.html#Report-4

branches: 1.1.1;
Initial revision

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

More cleanup of #includes

branches: 1.1.1;
Initial revision

s/curent/current/ in comment.

More cleanup of #includes

branches: 1.1.1;
Initial revision

More cleanup of #includes

branches: 1.1.1;
Initial revision

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.6.2;
fix various typos in comments.

s/alpahbetics/alphabetics/ in comment.

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.3.2;
Fix inverted arguments in MGET().

branches: 1.2.14;
More cleanup of #includes

branches: 1.1.1;
Initial revision

More cleanup of #includes

branches: 1.1.1;
Initial revision

More cleanup of #includes

branches: 1.1.1;
Initial revision

Resolve conflicts

branches: 1.2.2;
KNF. Remove extra spaces. No functional change.

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

- Eliminate the global "boottime" variable, which was being accessed
without any synchronization against changes by e.g. clock_settime().
- Replace with new getbinboottime() / getnanoboottime() / getmicroboottime()
functions (naming mirrors that of other time access functions in kern_tc.c).
It returns the (maybe-converted) value of timebasebin, which also tracks
our estimate of when the system was booted (i.e. the legacy "boottime" was
redundant).

XXX There needs to be a lockless synchronization mechanism for reading
timebasebin, but this is a problem in kern_tc.c that pre-existed these
"boottime" changes. At least now the problem is centralized in one location.

branches: 1.2.16;
More cleanup of #includes

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

branches: 1.1.2; 1.1.4; 1.1.18;
Add the initial module(9) infrastructure

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

branches: 1.1.1;
Initial revision

More cleanup of #includes

branches: 1.1.1;
Initial revision

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Update to FreeBSD revision 308975 ( approx 2016-11-18 07:30 UTC)

If I'm going to try to get this working, I should at least start with
the most recent code available.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10; 1.1.1.1.12; 1.1.1.1.16;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Disable duplicate typedef

branches: 1.1.1;
Initial revision

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

Resolve conflicts

branches: 1.2.2;
KNF. Remove extra spaces. No functional change.

branches: 1.1.1;
Initial revision

Remove unused (and a reference to ovbcopy along the way).

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

Clean up some #includes

branches: 1.1.1;
Initial revision

Update to FreeBSD revision 308975 ( approx 2016-11-18 07:30 UTC)

If I'm going to try to get this working, I should at least start with
the most recent code available.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10; 1.1.1.1.12; 1.1.1.1.16;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Mostly mechanical updates for caddr_t, thread, mutex, and credentials

branches: 1.1.1;
Initial revision

fix a/an grammar in obvious cases

branches: 1.2.52;
Mostly mechanical updates for caddr_t, thread, mutex, and credentials

branches: 1.1.1;
Initial revision

Update to FreeBSD revision 308975 ( approx 2016-11-18 07:30 UTC)

If I'm going to try to get this working, I should at least start with
the most recent code available.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10; 1.1.1.1.12; 1.1.1.1.16;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

KNF. Remove extra spaces. No functional change.

branches: 1.1.1;
Initial revision

Update for location of newnfs headers, clean up some other #include

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Update for location of newnfs headers, clean up some other #include

branches: 1.1.1;
Initial revision

fix few typos and grammar in comments.

Update for location of newnfs headers, clean up some other #include

Resolve conflicts

branches: 1.2.2;
PR/50535: David Binderman: Fix nonsense strcmp

branches: 1.1.1;
Initial revision

Update for location of newnfs headers, clean up some other #include

branches: 1.1.1;
Initial revision

Update for location of newnfs headers, clean up some other #include

branches: 1.1.1;
Initial revision

Update for location of newnfs headers, clean up some other #include

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

Update for location of newnfs headers, clean up some other #include

branches: 1.1.1;
Initial revision

Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

branches: 1.1.1;
Initial revision

branches: 1.1.1.1.4; 1.1.1.1.6; 1.1.1.1.10;
Import FreeBSD's "newnfs" nfs client and server code. This contains
nfsv4 as well as new implementations of nfsv3 and nfsv2.

This import is from tonight's FreeBSD head and is unchanged from there
except for automated munging of rcsids, rearranging of paths, and an
autogenerated files.* file that might or might not be syntactically
valid. (I will check in the script that does this shortly.)

There is not the slightest chance this will configure yet, let alone
compile or run.

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.4.52;
Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

Resolve conflicts

branches: 1.2.4; 1.2.6; 1.2.10; 1.2.12; 1.2.16;
Change the queue.3 *_END(&head) macros to NULL. Since we don't have CIRCLEQ
anymore, all the macros expand to NULL anyway, so this improves readability.
Requested by rmind@

branches: 1.1.1;
Initial revision

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.4.52;
Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

Resolve conflicts

branches: 1.2.4; 1.2.6; 1.2.10; 1.2.12; 1.2.16;
kill sprintf.

branches: 1.1.1;
Initial revision

branches: 1.1.2; 1.1.4; 1.1.18;
Add the initial module(9) infrastructure

Don't use legacy VM types.

branches: 1.3.12; 1.3.14;
Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.2.14; 1.2.16;
Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

branches: 1.1.1;
Initial revision

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.5.2;
fix various typos in comments.

Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

Resolve conflicts

branches: 1.2.4; 1.2.6; 1.2.10; 1.2.12; 1.2.16;
kill sprintf.

branches: 1.1.1;
Initial revision

Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

branches: 1.1.1;
Initial revision

sys: Drop redundant NULL check before m_freem(9)

m_freem(9) safely has accepted NULL argument at least since 4.2BSD:
https://www.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_mbuf.c

Compile-tested on amd64/ALL.

Suggested by knakahara@

branches: 1.5.6;
s/Resture/Restore/ and s/restared/restarted/ in comments.

Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

Resolve conflicts

branches: 1.2.4; 1.2.6; 1.2.10; 1.2.12; 1.2.16;
Change the queue.3 *_END(&head) macros to NULL. Since we don't have CIRCLEQ
anymore, all the macros expand to NULL anyway, so this improves readability.
Requested by rmind@

branches: 1.1.1;
Initial revision

Update locations for new nfs header files.

XXX Some #includes are just disabled (via #if 0) and will need to be
XXX resolved before further progress can be made.

Resolve conflicts

branches: 1.2.2; 1.2.4;
src is too big these days to tolerate superfluous apostrophes. It's
"its", people!

branches: 1.1.1;
Initial revision