d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
95,683 Commits 4 Branches 49 Tags
Commit Graph

95683 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
peter
39da8f45bd Fix a 64 bit time_t bogon that I missed from before. lastlog.ll_time is 
not a time_t.
 2003-10-26 06:01:06 +00:00
peter
18ddddadd0 Use -fno-builtin-log. Fix svc_sendreply() missing required casts. 
It is now WARNS=2 clean again.
 2003-10-26 05:58:21 +00:00
peter
84984af725 Use -fno-builtin-log so gcc doesn't get ideas about using a math function 
to log data.  Clean up an unused variable that was hidden by the WARNS?=2
being commented out.  Uncomment it now that it compiles cleanly again.
 2003-10-26 05:54:07 +00:00
peter
8acbfb4949 Make this compile cleanly. Switch to using rpcgen to generate 
code that can be compiled on an ansi-C compiler, so that it puts the
xdrproc_t casts in.  This also implies a slight function name change.
 2003-10-26 05:51:51 +00:00
imp
2005ad145d Style changes: 
o kill register
o minor function name tweaks.
 2003-10-26 05:34:01 +00:00
peter
c64cf72312 Make 64 bit safe. 2003-10-26 05:33:59 +00:00
peter
7b2e1ddf31 Fix up warnings. There were some biggies here. There seems to be two 
different sets of definitions in /usr/include/rpcsvc, mostly compatable,
but with different names.  Will the real one please stand up?
In order to get prototypes for yp_maplist, we had to use the 'other'
naming system.
 2003-10-26 05:30:40 +00:00
peter
a799821e85 Stop gcc warnings 2003-10-26 05:28:01 +00:00
peter
c8ef24efda Prototype yp_maplist() 2003-10-26 05:27:14 +00:00
peter
a4f43a8a53 Fix a warning that showed up on 64 bit systems. It was actually a real 
bug that had been swept under the carpet.
 2003-10-26 05:05:48 +00:00
peter
57e85f6680 Fix warning about cgetent() argument. 2003-10-26 05:03:11 +00:00
peter
6281d6e071 More xdrproc_t issues. 2003-10-26 04:58:44 +00:00
peter
03863a4dc2 More xdrproc_t warnings. 2003-10-26 04:57:32 +00:00
peter
fc696c9d63 The math function logf() probably isn't doing us much good for logging 
stuff.  Add -fno-builtin-logf.
 2003-10-26 04:49:58 +00:00
peter
29ac737336 Fix some 64 bit warnings. You can't fit a pointer in an int. 2003-10-26 04:47:31 +00:00
peter
96896379b8 Fix a 64 bit warning. Have set_T_dev_t() take a pointer to a size_t rather 
than a pointer to an int, since that is what it really wants anyway.
 2003-10-26 04:45:08 +00:00
peter
998da918d9 Fix gcc warnings. If NAME_MAX is 255, and d_namlen is a uint8_t, then 
d_namlen can never be > NAME_MAX.  Stop gcc worrying about this by
using a preprocessor test to see if NAME_MAX changes.
 2003-10-26 04:43:02 +00:00
peter
4550cc64c2 64 bit fixes. in_addr_t is an uint32_t, not a u_long. 2003-10-26 04:37:57 +00:00
peter
7f6ed48f65 Give wider types to sscanf to fix two warnings (u_short cannot be > 0xffff) 
and to make sure that we catch oversized arguments rather than silently
truncate them.  I dont know if sscanf will reject an integer if it will
not fit in the short return variable or not, but this way it should be
detected.
 2003-10-26 04:36:47 +00:00
peter
b35f301d40 Tidy up some xdrproc_t related warnings. 2003-10-26 04:32:53 +00:00
peter
9e4da6dd3b Pacify gcc warning with a Douglas Adams reference. 2003-10-26 04:30:05 +00:00
peter
9ff77005b4 Fix some warnings by defining has_sa_sigaction to 1. When the configure 
script was run (years and years ago), we didn't have it.
 2003-10-26 04:26:52 +00:00
peter
ad3ca1dde1 Since I'm having so much fun with const, beat my head against the wall 
some more.  Make this compile cleanly.
 2003-10-26 04:20:19 +00:00
peter
bfcf5b3a91 Pointers dont fit in an int on 64 bit platforms. Fix a gcc warning. 2003-10-26 04:12:02 +00:00
peter
b84f0fd155 The third arg to strncmp() is size_t, not int. This causes a warning on 
systems where size_t is long, not int.
 2003-10-26 04:10:50 +00:00
peter
92983ccab1 Preserve the constness of the value argument passed to env_setenv() as 
it gets passed through the filter functions.
 2003-10-26 04:04:12 +00:00
peter
cb29a24d26 Pacify gcc about casting pointers to integers (for the lowest few bits). 2003-10-26 03:55:58 +00:00
peter
79a9b01a78 (mostly) Clean up some const warnings here. The code takes some liberties 
because it is the originator of various const strings and knows that they
came from malloc.
 2003-10-26 03:51:47 +00:00
peter
eaeee19e67 clnt_call takes args of type xdrproc_t. 2003-10-26 03:43:35 +00:00
peter
7c422b97bd Move the -Wtraditional warning from the global cpp flags to when the -p 
(portability warnings) switch is used.  Add -Wno-system-headers after it so
that we dont get 500 screenfulls of warnings about #elif in /usr/include.
I'm not entirely happy with this.  Maybe cdefs.h shouldn't use #elif and
instead nest #else clauses?
 2003-10-26 03:34:13 +00:00
peter
f121e493d5 Disable the log() builtin (the math function), because it will not do much 
logging of information like the program expects.
 2003-10-26 03:15:54 +00:00
peter
ee993cd50a When we pass a string as auxillary data (type long), be sure to convert 
it to a suitable type for the initialization.
 2003-10-26 03:12:47 +00:00
peter
3957af6745 Fix a warning about mismatched pointers. A pointer to "void *" is not the 
same as a pointer to "char *".  Tell the compiler this is ok.
 2003-10-26 03:01:24 +00:00
alfred
bc96d82ac8 constify bintime_add, bintime_sub, bintime2timespec, timespec2bintime, 
bintime2timeval and timeval2bintime.
 2003-10-26 02:38:34 +00:00
alfred
4ba4eee48e constify the second args to timevaladd() and timevalsub(). 2003-10-26 02:19:00 +00:00
grog
330554451e Add coup d'état in Chile, 1973. 2003-10-26 01:18:08 +00:00
imp
7a210cb6a4 Const poison string accessor functions. 2003-10-26 00:51:40 +00:00
trhodes
f5b54933f1 style.Makefile: Add a '?' before '=' in WARNS. 2003-10-26 00:35:05 +00:00
grog
8a69810aef Add end and start dates for DST. 2003-10-26 00:03:49 +00:00
phk
a98bdabe34 Consistently cast to (u_char *) when filling with junk. 2003-10-25 23:47:33 +00:00
alc
23a376f078 - Add some of the required vm object locking, including assertions where 
the vm object lock is required and already held.
 2003-10-25 23:42:17 +00:00
jmg
66ca0a8b51 fix spelling of ATTACH 
Submitted by:	Johny Mattsson
MFC after:	2 week
(do to code freeze)
 2003-10-25 22:03:10 +00:00
imp
a499536827 Minor style nits suggested by sam and mdodd: 
o give an argument to EP_BUSY_WAIT
o use foo_locked rather than foo_body
o Add locking assertions for extra safety.
 2003-10-25 21:28:40 +00:00
imp
08148c6afb Convert to bus_space. 
Make the pccard attachment work with NEWCARD
Start locking of the driver, but only the macros are defined right now

Tested on: Megahertz CC10BT/2
# (These cards are very popular on ebay these days, and run < $10 including
#  shipping from some sellers).
 2003-10-25 19:56:19 +00:00
des
a7b0d81550 Better safe than clever. 
Submitted by:	das
 2003-10-25 19:53:28 +00:00
peter
537239cace For the SMP case, flush the TLB at the beginning of the page zero/copy 
routines.  Otherwise we run into trouble with speculative tlb preloads
on SMP systems.  This effectively defeats Jeff's revision 1.438
optimization (for his pentium4-M laptop) in the SMP case.  It breaks
other systems, particularly athlon-MP's.
 2003-10-25 18:51:41 +00:00
alc
92470025a7 - Align a comment within struct vm_page. 
- Annotate the vm_page's valid field as synchronized by the containing
   vm object's lock.
 2003-10-25 18:33:04 +00:00
rwatson
b43632b153 Check (locked) before performing an advisory unlock following a failure 
of vn_start_write().  Otherwise, we may inconsistently attempt to release
the advisory lock.

Pointed out by:	teggej
 2003-10-25 16:43:50 +00:00
rwatson
e4935eb9ae When generate a core dump, use advisory locking in an advisory way: 
if we do acquire an advisory lock, great!  We'll release it later.
However, if we fail to acquire a lock, we perform the coredump
anyway.  This problem became particularly visible with NFS after
the introduction of rpc.lockd: if the lock manager isn't running,
then locking calls will fail, aborting the core dump (resulting in
a zero-byte dump file).

Reported by:	Yogeshwar Shenoy <ynshenoy@alumni.cs.ucsb.edu>
 2003-10-25 16:14:09 +00:00
rwatson
723804b261 Allow MAC policies to block/revoke kern_alq write access to a file. 
Obtained from:	TrustedBSD Project
Sponsored by:	DARPA, Network Associates Laboratories
Reviewed by:	jeff
 2003-10-25 16:10:41 +00:00