| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
- Don't use u_char and u_int in userland.
- Change 'unsigned' to 'unsigned int'.
- Update copyright years.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: OpenBSD
MFC after: 1 week
|
|
|
|
|
|
|
| |
This ensures the same encryption key won't be used for more than
2^20 blocks (sectors). This will be the default now.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add "children" [1]
- Add "acknowledgement", "acknowledgment", "Austria" and "haunted" [2]
- Add "near", "antidisestablishmentarianism" and "Persephone" [2]
- "Transvaal" should be capitalized [2]
- Correct spelling of "structurelessness" and "Athena" [2]
- Add missing atomic elements [3]
- Add various words from "word of the day" lists [3]
PR: conf/149756 [1]
Submitted by: Nick Johnson <freebsd spatula.net> [1]
Obtained from: NetBSD [2], OpenBSD [3]
MFC after: 1 week
|
|
|
|
|
|
| |
- Flush write cache after each write.
MFC after: 1 week
|
|
|
|
|
|
| |
- fsync() created filed.
MFC after: 1 week
|
|
|
|
|
|
|
| |
don't want situation where old size is equal to new size, as we will trash
newly written metadata.
MFC after: 1 week
|
|
|
|
|
|
| |
- Flush cache after writing metadata.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
debugging purposes only.
MFC after: 3 days
|
|
|
|
| |
without a -m option. -m mips is still not supported)
|
|
|
|
|
|
|
| |
XLS MIPS processor).
Submitted by: Sreekanth M. S. <kanthms at netlogicmicro dot com>
Reviewed by: mav
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
not optimal from a performance standpoint since the write buffer is
not necessarily be filled up when the inflate rountine reached the
end of input buffer and it's not the end of file.
This problem gets uncovered by trying to pipe gunzip -c output to
a GEOM device directly, which enforces the writes be multiple of
sector size.
Sponsored by: iXsystems, Inc.
Reported by: jpaetzel
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
btohs() and btohl()
PR: kern/136386
Submitted by: Monty Hall < kungfu_disciple at sbcglobal dot net >
MFC after: 1 week
|
|
|
|
|
| |
PR: 150504
Submitted by: Douglas Berry <bitnix@bitnix.ca>
|
|
|
|
|
|
| |
PR: 150504
Submitted by: Douglas Berry <bitnix@bitnix.ca>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
driver-maintained ifnet fields (such as if_drv_flags).
- Use soft locks as the mutex that protects each interface's knote list
rather than using the global knote list lock. Also, use the softc
for kn_hook instead of the cdev.
- Use mtx_sleep() instead of tsleep() when blocking in the read routines.
This fixes a lost wakeup race.
- Remove D_NEEDGIANT now that the cdevsw routines use the softc lock
where locking is needed.
- Lock IFQ when calculating the result for FIONREAD in tap(4). tun(4)
already did this.
- Remove remaining spl calls.
Submitted by: Marcin Cieslak saper of saper|info (3)
MFC after: 2 weeks
|
|
|
|
|
| |
avoids spinning in an infinite loop for some (possibly corrupt?) core
files at work.
|
| |
|
|
|
|
|
|
|
|
|
| |
This way the primary process inherits signal mask from the main process,
which fixes a race where signal is delivered to the primary process before
configuring signal mask.
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
while the main process sends control message to the worker process, but worker
process hasn't started control thread yet, because it waits for reply from the
main process.
The fix is to start the control thread before sending any events.
Reported and fix suggested by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
| |
socket pairs. We did that only in one case out of three.
MFC after: 3 days
|
|
|
|
|
| |
terms of the arguments that configure was called with is misleading because
if IPv6 support is present on the system it will be present in BIND.
|
|
|
|
|
|
| |
process died. Instead of entering infinite loop, terminate.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Approved by: pgollucci (mentor)
|
| |
|
|
|
|
| |
I do not believe there is any functional change.
|
|
|
|
|
|
|
|
|
|
| |
the location, apply elf_relocaddr to the symbol value to have right
values for the symbols from dpcpu segment.
PR: kern/147769
Discussed with: avg
Tested by: marius
MFC after: 2 weeks
|
|
|
|
| |
That caused LAPIC timer failure and huge delays during boot on some systems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a followup to r212964.
stack_print call chain obtains linker sx lock and thus potentially may
lead to a deadlock depending on a kind of a panic.
stack_print_ddb doesn't acquire any locks and it doesn't use any
facilities of ddb backend.
Using stack_print_ddb outside of DDB ifdef required taking a number of
helper functions from under it as well.
It is a good idea to rename linker_ddb_* and stack_*_ddb functions to
have 'unlocked' component in their name instead of 'ddb', because those
functions do not use any DDB services, but instead they provide unlocked
access to linker symbol information. The latter was previously needed
only for DDB, hence the 'ddb' name component.
Alternative is to ditch unlocked versions altogether after implementing
proper panic handling:
1. stop other cpus upon a panic
2. make all non-spinlock lock operations (mutex, sx, rwlock) be a no-op
when panicstr != NULL
Suggested by: mdf
Discussed with: attilio
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
address spaces
There has been no need to do that starting with ACPICA 20040427 as
AcpiEnableSubsystem() installs the handlers automatically.
Additionaly, explicitly calling AcpiInstallAddressSpaceHandler before
AcpiEnableSubsystem is not supported by ACPICA and leads to too early
execution of _REG methods in some DSDTs, which may result in problems.
Big thanks to Robert Moore of ACPICA/Intel for explaining the above.
Reported by: Daniel Bilik <daniel.bilik@neosystem.cz>
Tested by: Daniel Bilik <daniel.bilik@neosystem.cz>
Reviewed by: jkim
Suggested by: "Moore, Robert" <robert.moore@intel.com>
MFC after: 1 week
|
|
|
|
| |
to handle it.
|
|
|
|
| |
kernel dump time, especially with minidump.
|
|
|
|
|
|
|
|
|
|
| |
slice they are on. When NANO_LABEL is not defined, the fstab
generates entries that specify /dev/ad0s1a. When NANO_LABEL is
defined, it generates /dev/usb/${NANO_LABEL}s1a. The prior code
created the file system with a label of ${NANO_LABEL}s1, leading to
problems on boot.
Pointy hat to: imp@
|
|
|
|
|
|
|
| |
Mappings with other cacheability attributes can be established, if needed,
by using 'pmap_kenter_attr()'.
Suggested by: jchandra, imp
|
|
|
|
|
|
|
|
|
|
| |
Buffalo (Melco Inc.) LUA3-U2-AGT
Logitec LAN-GTJ/U2A(usb/119981)
PR: usb/119981 and me
Submitted by: "Y.Okabe" <be_works_us at yahoo.com>, hiroo at oikumene.gcd.org
Reviewed by: thompsa
MFC after: 3 days
|