| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
over building gcc and binutils. They default to true, unless
MK_TOOLCHAIN is no.
Reviewed by: ru@
|
|
|
|
|
|
|
|
| |
- Use inet_ntop(3) instead of reimplementing it.
- Use %hhu for unsigned char instead of casting it to unsigned int and
using %u.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
and destroy_devl() drops dev_mtx. The protection against the race
with dev_rel(), introduced in r163328, should be extended to cover
destroy_devl() calls for the children of the destroyed dev.
Reported and tested by: joerg
MFC after: 1 week
|
|
|
|
|
|
| |
- Enable PCIe relaxed ordering for all egress queues and rx data buffers.
MFC after: 3 days
|
|
|
|
| |
Approved by: philip (mentor)
|
|
|
|
|
|
|
| |
Note: possible minor security issues fixed (untrusted string used as
printf format string).
Approved by: philip (mentor)
|
|
|
|
| |
Approved by: philip (mentor)
|
|
|
|
| |
Approved by: philip (mentor)
|
|
|
|
|
|
| |
Note: these were actually bugs (printf with no format string).
Approved by: philip (mentor)
|
|
|
|
|
|
|
|
|
|
| |
tables,
and other potential evil.
Submitted by: Kris Moore <kris@pcbsd.org>
Approved by: kib (mentor)
Sponsored by: iXsystems
|
|
|
|
|
|
| |
Submitted by: Kris Moore <kris@pcbsd.org>
Approved by: kib (mentor)
Sponsored by: iXsystems
|
|
|
|
|
| |
Reported by bz@
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
to both NFS clients. This avoids the crash reported by
Sergey Kandaurov (pluknet@gmail.com) to the freebsd-fs@
list with subject "[old nfsclient] different nmount()
args passed from mount vs mount_nfs" dated May 17, 2011.
Tested by: pluknet at gmail.com (old nfs client)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
so that running make release causes make obj to be run before doing
anything. This fixes a bug wherein, when run for the first time, and
without -DNOSRC, make release would attempt to recursively tar up the src
directory including its own output and enter an infinite loop.
While here, make the cross-building stuff work a little more the way it
should if only one of TARGET/TARGET_ARCH is specified.
|
|
|
|
|
|
|
|
| |
one. Without this, we don't have ar or randlib in the tool path,
leading to much pain for some users. This pain is exposed by the
external toolchain enhancements that I'm working on.
Submitted by: John Hein (ages ago, and dropped on the floor by me: sorry)
|
|
|
|
|
|
| |
largeSMP branch.
Reported by: pluknet
|
|
|
|
| |
Reported by: sbruno
|
|
|
|
| |
Reported by: sbruno
|
|
|
|
|
|
|
| |
Sync XEN support with i386 about the usage of ipi_send_cpu()
Tested by: pluknet
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
Submitted by: gcooper
Pointyhat to: avg
MFC after: 1 month
X-MFC with: r222051
|
| |
|
|
|
|
| |
Reviewed by: stass
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This brings USB bus more in line with how newbus is supposed to be used.
Also, because of the two-pass probing the following message was produced
by devd in default configuration when almost any USB device was
connected:
Unknown USB device: vendor <> product <> bus <>
This should be fixed now.
Note that many USB device drivers pass some information from probe
method to attach method via ivars. For this to continue working we rely
on the fact that the subr_bus code calls probe method of a winning driver
again before calling its attach method in the case where multiple
drivers claim to support a device. This is done because device
description is set in successful probe methods and we want to get a correct
device description from a winning driver. So now this logic is re-used
for setting ivars too.
Reviewed by: hselasky
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(zfs destroy -r pool/dataset@snapshot)
To destroy all descendent snapshots with the same name the top level
snapshot was not required to exist. So if the top level snapshot does
not exist, check permissions of the parent dataset instead.
Filed as Illumos Bug #1043
Reviewed by: delphij
Approved by: pjd
MFC after: together with v28
|
|
|
|
| |
rates for HT nodes.
|
|
|
|
|
|
|
|
|
| |
Note AMD dropped SSE5 extensions in order to avoid ISA overlap with Intel
AVX instructions. The SSE5 bit was recycled as XOP extended instruction
bit, CVT16 was deprecated in favor of F16C (half-precision float conversion
instructions for AVX), and the remaining FMA4 (4-operand FMA instructions)
gained a separate CPUID bit. Replace non-existent references with today's
CPUID specifications.
|
|
|
|
| |
Tested by: sbruno, pluknet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove the following sysctl:
kern.sched.ipiwakeup.onecpu
kern.sched.ipiwakeup.htt2
Because they are absolutely obsolete. Probabilly the whole wakeup
forward mechanism should be revisited for a better fitting in modern
hw, in the future.
- As map2 variable is no longer used rename map3 to map2
- Fix a string by making more informative the msg and removing the
arguments passing.
Reviewed by: julian
Tested by: several
|
|
|
|
|
|
|
|
|
| |
When supported by hardware, this allows to control per-port activity, locate
and fault LEDs via the led(4) API for localization and status reporting
purposes. Supporting AHCI controllers may transmit that information to the
backplane controllers via SGPIO interface. Backplane controllers interpret
received statuses in some way (IBPI standard) to report them using present
indicators.
|
|
|
|
|
|
| |
The declaration in the header file is correct.
MFC after: 1 week
|
|
|
|
| |
"#notimpressed" as my twittering friends would say.
|
|
|
|
| |
Discussed with: erwin, brooks, bapt
|
|
|
|
| |
Clarify return values.
|
|
|
|
|
| |
Instigate symbol versioning
Pray that I don't break the build.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
last CPU to to finish the rendezvous action may become visible to
different CPUs at different times. As a result, the CPU that initiated
the rendezvous may exit the rendezvous and drop the lock allowing another
rendezvous to be initiated on the same CPU or a different CPU. In that
case the exit sentinel may be cleared before all CPUs have noticed causing
those CPUs to hang forever.
Workaround this by using a generation count to notice when this race
occurs and to exit the rendezvous in that case.
The problem was independently diagnosted by mlaier@ and avg@ as well.
Submitted by: neel
Reviewed by: avg, mlaier
Obtained from: NetApp
MFC after: 1 week
|
| |
|
|
|
|
| |
MFC after: 1 week.
|
|
|
|
|
|
| |
Reported by scf@
MFC after: 1 week.
|
|
|
|
|
| |
Pointy hat goes to: adrian, for having multiple build screens
open and checking the wrong one.
|
|
|
|
| |
MFC after: 5 days
|
|
|
|
|
| |
- use a proper macro for interface name ipfw0.
- add missing section number for bpf cross reference.
|
|
|
|
|
|
|
|
|
| |
the multicast key search support for AR5212, AR5416 and later.
The general HAL routine ath_hal_getcapability() implement checking this
but it's overridden by a check in ar5212_misc:ar5212GetCapability().
This restores the later functionality in case it's found to be broken
in any of the 11n chipsets.
|
|
|
|
| |
being used.
|
|
|
|
|
| |
Reviewed by: hselasky
MFC after: 3 days
|
|
|
|
|
|
|
| |
to <dev/pci/pcireg.h>.
Reviewed by: hselasky
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is no relevant difference for sbufs, and it increases portability of
the source code.
Split the actual initialization of the sbuf into a separate local
function, so that certain static code checkers can understand
what sbuf_new() does, thus eliminating on silly annoyance of
MISRA compliance testing.
Contributed by: An anonymous company in the last business I
expected sbufs to invade.
|
|
|
|
|
|
|
|
| |
I checked with http://www.iso.org/iso/country_codes/iso_3166_code_lists.htm
and "MF" was officially spelled in English as "Saint Martin" there, but now
that "SX" exists (for "Sint Maarten (Dutch part)") (nice official "English"
spelling!) they seem to have added a "(French part)" suffix to "MF". Since
this is also in line with Newsletter VI-1 (2007-09-21), catch up.
|
|
|
|
| |
MFC after: 3 days
|