| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Also remove some local patches to diff(1) which are now unneeded.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A nice thing about POSIX 2008 is that it finally standardizes a way to
obtain file access/modification/change times in sub-second precision,
namely using struct timespec, which we already have for a very long
time. Unfortunately POSIX uses different names.
This commit adds compatibility macros, so existing code should still
build properly. Also change all source code in the kernel to work
without any of the compatibility macros. This makes it all a less
ambiguous.
I am also renaming st_birthtime to st_birthtim, even though it was a
local extension anyway. It seems Cygwin also has a st_birthtim.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Submitted by: sam
> Description of fields to fill in above: 76 columns --|
> PR: If a GNATS PR is affected by the change.
> Submitted by: If someone else sent in the change.
> Reviewed by: If someone else reviewed your modification.
> Approved by: If you needed approval for this commit.
> Obtained from: If the change is from a third party.
> MFC after: N [day[s]|week[s]|month[s]]. Request a reminder email.
> Security: Vulnerability reference (one per line) or description.
> Empty fields above will be automatically removed.
M ieee80211_hostap.c
|
|
|
|
|
|
|
|
| |
do not try to free the same list twice but free both the
acquiring list and the security policy acquiring list.
Reviewed by: anchie
MFC after: 3 days
|
|
|
|
|
|
| |
can be used in applications compiled with only POSIX types visible.
MFC after: 2 weeks
|
|
|
|
| |
X-MFC after: r205573
|
|
|
|
|
|
| |
version.
MFC after: 3 weeks
|
|
|
|
|
|
| |
connection timeouts.
Reported by: Kevin Day <toasty@dragondata.com>
|
|
|
|
| |
PR: kern/145081
|
|
|
|
|
|
|
| |
Fix some wrong usages.
Note: this does not affect generated binaries as this argument is not used.
Approved by: harti@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
parser. This merge does not change any API and should not break any
native or thirdparty applications.
Changes include:
* Merge multiple report ID support and other improvements from kernel
HID parser.
* Ignore rid argument in hid_start_parser, parse all the report items since
we now support multiple report ID.
* Skip report ID byte in hid_get_data() and set report ID byte in
hid_set_data(), if report ID is non-zero.
* Reimplement hid_get_report_id: instead get report id from uhid device
(which is always 0), try parsing the report descriptor and return the
first report ID encountered.
Reviewed by: hps
Silent on: -usb mailing list
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Switch to ITANIUM2 has the cpu. This has absolutely no effect
on the code, but makes for a better example.
o Drop COMPAT_FREEBSD6. We're tier 2, so you're supposed to run
8-stable or newer.
o Add PREEMPTION. It works now.
o Remove HWPMC_HOOKS. We don't have support for hwpmc yet.
o Add a bunch of new devices: atapist, hptiop, amr, ips, twa, igb,
ixgbe, ae, age, alc, ale, bce, bfe, et, jme, msk, nge, sk, ste,
stge, tx, vge, axe, rue, udav, fwip, and all USB serial.
o Remove "legacy" devices: le, vx, dc, pcn, rl, sis.
Make sure to the module list is a superset of what goes into GENERIC.
|
|
|
|
|
| |
round-robin fashion, starting with the highest priority interrupt
on the highest-numbered CPU and cycling downwards.
|
| |
|
|
|
|
|
|
| |
with PCI busses. Remove nexus_read_ivar() and nexus_write_ivar()
to give default behaviour. Remove <machine/nexusvar.h> as well,
because there's nothing in it that's being used.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- add some new hardware support for 82599
- Big change to interrupt architecture, it now
uses a queue which contains an RX/TX pair as
the recipient of the interrupt. This will reduce
overall system interrupts/msix usage.
- Improved RX mbuf handling: the old get_buf routine
is no longer synchronized with rxeof, this allows
the elimination of packet discards due to mbuf
allocation failure.
- Much simplified and improved AIM code, it now
happens in the queue interrupt context and takes
into account both the traffic on the RX AND TX
side.
- variety of small tweaks, like ring size, that have
been seen as performance improvements.
- Thanks to those that provided feedback or suggested
changes, I hope I've caught all of them.
|
|
|
|
|
|
|
|
| |
to ia64_enable_intr(). This reduces confusion with intr_disable() and
intr_restore().
Have configure_final() call ia64_finalize_intr() instead of enable_intr()
in preparation of adding support for binding interrupts to all CPUs.
|
|
|
|
| |
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that this is actually a no-op for most users, as this GNU
cpio was broken on -HEAD and 8-STABLE since last March until
the recent fix.
FreeBSD 8.0+ uses BSD cpio by default and the code is being
actively maintained.
Blessed by: kientzle
With hat: secteam
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
on debug output. Add a new platform function requirement to allow
for printing based upon the ITL nexus instead of the isp unit plus
channel, target and lun. This allows some printouts and error messages
from the core code to appear in the same format as the platform's
subsystem (in FreeBSD's case, CAM path).
MFC after: 1 week
|
|
|
|
|
|
| |
build or use of linprocfs, before committing the reworked patch again.
Requested by: des
|
|
|
|
|
|
| |
Return an error immediatly in case of hard shutdown.
MFC after: 3days
|
|
|
|
| |
MFC after: 3days
|
| |
|
|
|
|
|
|
| |
Submitted by: Petr Salinger <Petr.Salinger@seznam.cz>
Verified on: GNU/kFreeBSD debian 8.0-1-686 (by submitter)
PR: 144584
|
|
|
|
|
|
| |
can't succeed for CREATE, DELETE and RENAME.
Discussed with: bde
|
|
|
|
|
|
| |
- add quirks for the usb storage
Reviewed by: hselasky
|
|
|
|
|
|
| |
same as Intel MatrixRAID does.
PR: kern/124064
|
| |
|
|
|
|
|
|
|
| |
- right order of src and dst in memcpy
- NULL out the clips after freeing to prevent an accident
Noticed by: hselasky
|
|
|
|
|
|
| |
Obtained from NetBSD.
Suggested by: jmallett@
|
|
|
|
|
|
| |
PR: docs/145031
Submitted by: olgeni
MFC after: 1 week
|
|
|
|
|
|
| |
PR: docs/145030
Submitted by: olgeni
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
have the BSP use IPIs to trigger clock interrupts on the APs.
This allows us to run on hardware configurations for which the
ITC has non-uniform frequencies across CPUs.
While here, change the clock XIV to type IPI so as to protect
the interrupt delivery against CPU re-balancing once that's
implemented.
|
|
|
|
|
|
|
| |
for the regular NFS server, to ensure that ESTALE is
returned to the client for all errors returned by VFS_FHTOVP().
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
call it "x86" instead of "i386".
Suggested by: jhb in response to Alexander Best's loader proposal
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
for all errors returned by VFS_FHTOVP(). This is required to ensure
that EIO doesn't get returned to the client when ZFS is used as the
server file system.
Tested by: korvus AT comcast.net
Reviewed by: jhb
MFC after: 2 weeks
|
|
|
|
| |
Pointy hat to: me
|
|
|
|
|
|
|
|
| |
PR: 144984
Submitted by: mm@
Approved by: pjd@
Obtained from: OpenSolaris
MFC after: 4 days
|
|
|
|
|
|
|
|
|
| |
When gl_pathc == 0, the content of gl_pathv is undefined.
PR: bin/144761
Submitted by: David BERARD <contact davidberard fr>
Obtained from: OpenBSD
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
remote tape service returns deliberately crafted packets containing
more data than requested.
Fix this by checking the returned amount of data and bail out when it
is more than what we requested.
PR: gnu/145010
Submitted by: naddy
Reviewed by: imp
MFC after: immediately
Security: CVE-2010-0624
|
|
|
|
|
| |
VBE function. Most problems should be corrected by the mode table sanity
check and we only need the paranoid in extremely rare cases.
|
|
|
|
|
|
|
|
| |
of another process. Modify pmap_promote_pde() to handle this. (This is
not a problem on amd64 due to implementation differences.)
Reported by: jh@
MFC after: 1 week
|
|
|
|
| |
read request size.
|
|
|
|
|
| |
Note I am keeping %ds change because X.org int10 handler does it and
it seems reasonable.
|
| |
|
|
|
|
|
|
|
|
|
| |
within the VBE interrupt handler. Unfortunately it was causing real mode
page faults because we were fetching instructions from bogus addresses.
Pass me the pointyhat, please.
PR: kern/144654
MFC after: 3 days
|