| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Submitted by: Ben Kaduk <minimarmot gmail com>
MFC after: 3 days
|
|
|
|
|
|
|
| |
interrupt-only GPIOs. Honor this, and allow interrupt attachment, but not
read/write access for such devices.
Reported by: Niels Eliasen
|
|
|
|
|
| |
Reviewed by: trhodes, keramida
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
some confusion when reading the manual page.
PR: 117798
Discussed with: keramida, brueffer
Recommended by: phk
|
|
|
|
| |
remove historic assertion that labels are always present.
|
| |
|
|
|
|
| |
Submitted by: "Jared Go" <jared@hobnob.com>
|
|
|
|
|
|
|
|
| |
mountand jail-aware file systems as well as quota.
PR: kern/68192
Reviewed by: simon
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
vnodes.
Reviewed by: kib
Approved by: rwatson (mentor)
Sponsored by: FreeBSD Foundation
|
| |
|
|
|
|
|
|
|
|
| |
many writes queued up.
Reviewed by: phk, scottl
Approved by: rwatson (mentor)
Sponsored by: FreeBSD Foundation
|
|
|
|
| |
VIA VT1708B and Realtek ALC268.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the loopback and synthetic loopback code so that packets are
access control checked and relabeled. Previously, the MAC
Framework enforced that packets sent over the loopback weren't
relabeled, but this will allow policies to make explicit choices
about how and whether to relabel packets on the loopback. Also,
for SIMPLEX devices, this produces more consistent behavior for
looped back packets to the local MAC address by labeling those
packets as coming from the interface.
Discussed with: csjp
Obtained from: TrustedBSD Project
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed by: imp (earlier version of patch)
|
|
|
|
| |
This makes OSSv4 osstest tool work.
|
| |
|
|
|
|
|
| |
Implement some OSSv4 ioctls to make ossinfo tool work and print
something reasonable.
|
|
|
|
|
|
|
|
|
|
| |
things around so the periph destructors look alike. Based on a patch
by Jaakko Heinonen.
Submitted by: Jaakko Heinonen
Reviewed by: scottl
Approved by: rwatson (mentor)
Sponsored by: FreeBSD Foundation
|
|
|
|
|
|
| |
Reviewed by: scottl
Approved by: rwatson (mentor)
Sponsored by: FreeBSD Foundation
|
|
|
|
|
| |
Submitted by: Andriy Gapon <avg icyb net ua>
MFC after: 3 days
|
| |
|
|
|
|
| |
Submitted by: jmc@OpenBSD.org
|
|
|
|
|
| |
PR: bin/124724
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
they label, derive that information implicitly from the set of label
initializers in their policy operations set. This avoids a possible
class of programmer errors, while retaining the structure that
allows us to avoid allocating labels for objects that don't need
them. As before, we regenerate a global mask of labeled objects
each time a policy is loaded or unloaded, stored in mac_labeled.
Discussed with: csjp
Suggested by: Jacques Vidrine <nectar at apple.com>
Obtained from: TrustedBSD Project
Sponsored by: Apple, Inc.
|
|
|
|
|
|
|
| |
MPC_OBJECT_IPQ; it was already defined, just not used.
Obtained from: TrustedBSD Project
Sponsored by: Apple, Inc.
|
|
|
|
|
|
|
| |
referenced in the sysctl req argument.
Reviewed by: rwatson
MFC after: 2 weeks
|
|
|
|
| |
Reviewed by: core
|
|
|
|
|
|
| |
Reported by: Richard Todd <rmtodd@ichotolot.servalan.com>
Reviewed by: kib
Approved by: kib
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
read with libkvm) to the addresses of a prison, when inside a
jail. [1]
As the patch from the PR was pre-'new-arp', add checks to the
llt_dump handlers as well.
While touching RTM_GET in route_output(), consistently use
curthread credentials rather than the creds from the socket
there. [2]
PR: kern/68189
Submitted by: Mark Delany <sxcg2-fuwxj@qmda.emu.st> [1]
Discussed with: rwatson [2]
Reviewed by: rwatson
MFC after: 4 weeks
|
|
|
|
|
|
| |
probably needs cleanups to be less specific to my needs/uses
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
Correct some minor whitespace in the ae(4) entry.
Reported by: Mars G Miro
Approved by: rwatson (mentor)
MFC after: 1 week
|
|
|
|
| |
Noticed-by: julian
|
|
|
|
| |
Thanks Max!
|
|
|
|
| |
for suggesting this.
|
|
|
|
|
|
| |
Nitpicking by: mlaier
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
| |
locking but the credential from curthread (usually) never changes.
Discussed with: jhb
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
applications to specify a non-local IP address when bind()'ing a socket
to a local endpoint.
This allows applications to spoof the client IP address of connections
if (obviously!) they somehow are able to receive the traffic normally
destined to said clients.
This patch doesn't include any changes to ipfw or the bridging code to
redirect the client traffic through the PCB checks so TCP gets a shot
at it. The normal behaviour is that packets with a non-local destination
IP address are not handled locally. This can be dealth with some IPFW hackery;
modifications to IPFW to make this less hacky will occur in subsequent
commmits.
Thanks to Julian Elischer and others at Ironport. This work was approved
and donated before Cisco acquired them.
Obtained from: Julian Elischer and others
MFC after: 2 weeks
|
|
|
|
|
|
| |
PR: 130324
Submitted by: Jaakko Heinonen <jh@saunalahti.fi>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
jail-aware. Up to now we returned the first address of the interface
for SIOCGIFADDR w/o an ifr_addr in the query. This caused problems for
programs querying for an address but running inside a jail, as the
address returned usually did not belong to the jail.
Like for v6, if there was an ifr_addr given on v4, you could probe
for more addresses on the interfaces that you were not allowed to see
from inside a jail. Return an error (EADDRNOTAVAIL) in that case
now unless the address is on the given interface and valid for the
jail.
PR: kern/114325
Reviewed by: rwatson
MFC after: 4 weeks
|
|
|
|
|
| |
Some 88F5182-based systems (Linkstation) have problems when PCIE is
accessed without any peripherals present.
|
| |
|
|
|
|
| |
Spotted by: Bjoern Voigt <bjoern@cs.tu-berlin.de>
|
|
|
|
|
| |
so that generic routing message parsing code can parse the messages for
L2 info that are retrieved via the sysctl interface.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- The contents of 'feroceon_cpufuncs' dispatch table was really dedicated for the
new Sheeva CPU (in 88F6xxx and MV-78xxx SOCs), and NOT Feroceon.
- Feroceon CPU (in 88F5xxx SOCs) appears as a regular ARM926EJ-S core and does
not require dedicated routines.
This will be accompanied by a file rename commit.
|