| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
transfers. The necessary context for calling copyin() isn't available
anyway and automatic code-validation chokes on this.
|
|
|
|
|
|
|
|
|
| |
for the vast majority of our cards. However, they are critically
needed to distinguish different fe based PC Cards (the FMV-182 from
the 182A) which need to be treated differently (the ethernet address
is loaded not from the standard CIS-based ethernet tuples, but from
differing locations in attribute space based on the version string in
CIS3. This should have no impact for other users of this function.
|
|
|
|
| |
Submitted by: ru
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for libarchive error messages. Mostly, this
avoids a portability headache related to
copying va_list arguments (some FreeBSD 5
platforms require va_copy; FreeBSD 4 doesn't
support va_copy at all). It also dramatically reduces the
size of libarchive for embedded applications:
a minimal "untar" program using libarchive can now be
under 64k statically linked (as opposed to ~100k
using library *printf() functions).
MFC after: 14 days
|
|
|
|
|
|
|
| |
Also break long lines -- note that the '\' must be up against the last
character of a line to keep command-line spacing proper.
Requested by: rwatson
|
|
|
|
|
|
|
|
|
| |
unhappiness lately.
As far as I can tell, no files that have made it safely to disk
have been endangered, but stuff in transit has been in peril.
Pointy hat: phk
|
| |
|
|
|
|
|
|
|
| |
T1.617 AnnexD.
Locking shift procedure is described in ANSI T1.607.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
| |
|
| |
|
| |
|
|
|
|
| |
Sort standard sections in the (documented) preferred order.
|
|
|
|
|
|
|
| |
of a structure for the sockaddr_in. Pass the pointer to connect()
instead of the pointer to the pointer.
Specify a port number to connect to.
|
| |
|
| |
|
|
|
|
|
| |
so that bus_dmamap_sync() knows what to invalidate. This makes em(4) work again.
While I'm there, remove the unused "first" variable.
|
|
|
|
|
|
|
| |
unfixed bug in the jail() implementation relating to using the connect()
system call on UDP sockets.
PR: 26506
|
| |
|
|
|
|
|
| |
in struct ip_fw_args itself.
- Remove redundant &= 0xffff from dummynet_io().
|
| |
|
|
|
|
|
| |
'usage: ' in front of usage string. Use warnx(3) instead of fprintf in error
messages to get progname prepended.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Introduce the amr_io_lock to control access to command queues, bio queues,
and the hardware.
- Eliminate the taskqueue and do all completion processing in the ithread.
- Assign a static slot number to each command instead of doing a linear
search for free slots each time a command is needed.
- Modify the interrupt handler to more closely match what Linux does, for
safety.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Obtained from: http://hpiers.obspm.fr/eoppc/bul/bulc/bulletinc.dat
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and BBO is BO's backing object. Now, suppose that O and BO are being
collapsed. Furthermore, suppose that BO has been marked dead
(OBJ_DEAD) by vm_object_backing_scan() and that either
vm_object_backing_scan() has been forced to sleep due to encountering
a busy page or vm_object_collapse() has been forced to sleep due to
memory allocation in the swap pager. If vm_object_deallocate() is
then called on BBO and BO is BBO's only shadow object,
vm_object_deallocate() will collapse BO and BBO. In doing so, it adds
a necessary temporary reference to BO. If this collapse also sleeps
and the prior collapse resumes first, the temporary reference will
cause vm_object_collapse to panic with the message "backing_object %p
was somehow re-referenced during collapse!"
Resolve this race by changing vm_object_deallocate() such that it
doesn't collapse BO and BBO if BO is marked dead. Once O and BO are
collapsed, vm_object_collapse() will attempt to collapse O and BBO.
So, vm_object_deallocate() on BBO need do nothing.
Reported by: Peter Holm on 20050107
URL: http://www.holm.cc/stress/log/cons102.html
In collaboration with: tegge@
Candidate for RELENG_4 and RELENG_5
MFC after: 2 weeks
|
|
|
|
| |
was really just a waste of cycles, so this streamlines it considerably.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Spotted out by: scottl
|
| |
|
| |
|
| |
|
|
|
|
| |
Obtained from: NetBSD
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without this fix, when ACLs are set via tunefs(8) on the root file system,
they are removed on boot when 'mount -a' is called, because mount(8)
called for the root file system always add MNT_UPDATE flag and MNT_UPDATE
flag isn't perfect.
Now, one cannot remove ACLs stored in superblock (configured with tunefs(8))
via 'mount -a' nor 'mount -u -o noacls <file system>', but it is still
possible to mount file system which doesn't have ACLs in superblock via
'mount -o acls <file system>' or /etc/fstab's 'acls' option.
Reported by: Lech Lorens/pl.comp.os.bsd
Discussed with: phk, rwatson
Reviewed by: rwatson
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
| |
Obtained from: NetBSD
|
|
|
|
|
|
| |
Make example locking calls in the EXAMPLES section.
Reviewed by: keramida
|