| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
we move towards netinet as a pseudo-object for the MAC Framework.
Rename 'mac_create_mbuf_linklayer' to 'mac_mbuf_create_linklayer' to
reflect general object-first ordering preference.
Sponsored by: SPARTA (original patches against Mac OS X)
Obtained from: TrustedBSD Project, Apple Computer
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
pkg_version tried to open instead of just "INDEX" to make the actual
problem more clear (e.g. missing INDEX-8).
MFC after: 3 days
Reviewed by: portmgr (pav)
|
|
|
|
| |
o Improve mdoc(7) markup and style of the paragraph on stop_boot.
|
|
|
|
| |
Add SATA ATAPI support for AHCI controllers.
|
| |
|
| |
|
|
|
|
| |
doing regression testing.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
kthread_add() takes the same parameters as the old kthread_create()
plus a pointer to a process structure, and adds a kernel thread
to that process.
kproc_kthread_add() takes the parameters for kthread_add,
plus a process name and a pointer to a pointer to a process instead of just
a pointer, and if the proc * is NULL, it creates the process to the
specifications required, before adding the thread to it.
All other old kthread_xxx() calls return, but act on (struct thread *)
instead of (struct proc *). One reason to change the name is so that
any old kernel modules that are lying around and expect kthread_create()
to make a process will not just accidentally link.
fix top to show kernel threads by their thread name in -SH mode
add a tdnam formatting option to ps to show thread names.
make all idle threads actual kthreads and put them into their own idled process.
make all interrupt threads kthreads and put them in an interd process
(mainly for aesthetic and accounting reasons)
rename proc 0 to be 'kernel' and it's swapper thread is now 'swapper'
man page fixes to follow.
|
|
|
|
|
|
| |
PR: 117512
Submitted by: Jeremy C. Reed <reed@reedmedia.net>
MFC after: 1 week
|
|
|
|
|
|
|
| |
in debug.ktr.mask. Because saving stack is very expensive, it's better only
to do it when one really wants to.
Reported by: Dan Nelson
|
| |
|
|
|
|
|
|
|
|
| |
refactored it to be a generic device.
Instead of being part of the standard kernel, there is now a 'nvram' device
for i386/amd64. It is in DEFAULTS like io and mem, and can be turned off
with 'nodevice nvram'. This matches the previous behavior when it was
first committed.
|
|
|
|
| |
Submitted by: csjp
|
|
|
|
| |
do this that should know better :-).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change introduces audit_proc_coredump() which is called by coredump(9)
to create an audit record for the coredump event. When a process
dumps a core, it could be security relevant. It could be an indicator that
a stack within the process has been overflowed with an incorrectly constructed
malicious payload or a number of other events.
The record that is generated looks like this:
header,111,10,process dumped core,0,Thu Oct 25 19:36:29 2007, + 179 msec
argument,0,0xb,signal
path,/usr/home/csjp/test.core
subject,csjp,csjp,staff,csjp,staff,1101,1095,50457,10.37.129.2
return,success,1
trailer,111
- We allocate a completely new record to make sure we arent clobbering
the audit data associated with the syscall that produced the core
(assuming the core is being generated in response to SIGABRT and not
an invalid memory access).
- Shuffle around expand_name() so we can use the coredump name at the very
beginning of the coredump call. Make sure we free the storage referenced
by "name" if we need to bail out early.
- Audit both successful and failed coredump creation efforts
Obtained from: TrustedBSD Project
Reviewed by: rwatson
MFC after: 1 month
|
|
|
|
|
| |
frequency. It'd be better to be able to calculate it at runtime, but we need
the information very early, to setup the uart.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
primary object type, and then by secondarily by method name. This sorts
entry points relating to particular objects, such as pipes, sockets, and
vnodes together.
Sponsored by: SPARTA (original patches against Mac OS X)
Obtained from: TrustedBSD Project, Apple Computer
|
| |
|
|
|
|
| |
Pointed out by: njl.
|
|
|
|
| |
Approved by: kib (mentor)
|
|
|
|
| |
Approved by: kib (mentor)
|
| |
|
|
|
|
|
|
| |
This breaks OSVERSION determination in all ports.
Reviewed by: rodrigc
|
|
|
|
|
|
|
|
|
|
| |
the PS/2 mouse controller. Thus, when acpi_ibm(4) claimed the mouse
device, the mouse would stop working. The one ACPI dump of an R40 that
I've looked at includes an HKEY device with the proper "IBM0068" ID, so
I'm not sure how the "IBM0057" ID could have helped at all.
MFC after: 1 week
Approved by: njl
|
| |
|
| |
|
|
|
|
|
|
| |
than always retrying operations three times.
Submitted by: nyan
|
| |
|
|
|
|
|
|
|
| |
other entry points in the form mac_<object>_method().
Discussed with: csjp
Obtained from: TrustedBSD Project
|
|
|
|
|
| |
Split the pc98_partition specific routine in bd_opendisk()
into bd_open_pc98().
|
| |
|
|
|
|
|
|
|
|
|
| |
Rework the read/write support in the bios disk driver some to cut down
on duplicated code.
- All of the bounce buffer and retry logic duplicated in bd_read() and
bd_write() are merged into a single bd_io() routine that takes an
extra direction argument. bd_read() and bd_write() are now simple
wrappers around bd_io().
|
|
|
|
| |
and bin/100443.
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
This includes fixes for FreeBSD PR's: bin/104795, bin/100443
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
from mac_vfs.c to mac_process.c to join other functions that setup up
process labels for specific purposes. Unlike the two proc create calls,
this call is intended to run after creation when a process registers as
the NFS daemon, so remains an _associate_ call..
Obtained from: TrustedBSD Project
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
than mac_<policy>_whatever, as this shortens the names and makes the code
a bit easier to read.
When dealing with label structures, name variables 'mb', 'ml', 'mm rather
than the longer 'mac_biba', 'mac_lomac', and 'mac_mls', likewise making
the code a little easier to read.
Obtained from: TrustedBSD Project
|
| |
| |
| |
| |
| |
| | |
version. While here, expand a macro only used once.
Discussed with/oked by: bde
|
| |
| |
| |
| |
| |
| | |
clean up some comments.
Obtained from: TrustedBSD Project
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
order. The kernel used to shuffle them around to get things right,
but that was recently fixed. This makes our boot loader match the
behavior of most other boot loaders for the atmel parts. This bug was
inherited from the Kwikbyte loader that we started from.
This bug was discovered by Bj.ANvrn KNvnig back in June, but fell on the
floor. He provided patches to the kernel, include backwards
compatibility options that were similar to Olivier's if_ate.c commit.
|
| |
| |
| |
| | |
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| | |
in the same order as it's set in ate_set_mac.
I remember a discussion about this on -arm, but apparently nothing was done.
Warner, is this wrong ?
X-MFC After: proper review
|
| |
| |
| |
| |
| |
| | |
at the beginning of the RAM).
MFC After: 1 week
|