| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- Whitespace fixes.
Submitted by: bde
|
|
|
|
|
| |
unload case of modules that use their own zones.
It has been tested with the nfs module.
|
|
|
|
| |
Reviewed by: jake
|
|
|
|
| |
characters) as sysctls (kern.tty_nin and kern.tty_nout).
|
|
|
|
|
| |
sys/devicestat.h, so that the queue can be walked in crashdumps using
libkvm.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
removing network card, and kill aplication.
imo_membership[].inm_ifp refer interface pointer
after removing interface.
When kill aplication, release socket,and imo_membership.
imo_membership use already not exist interface pointer.
Then, kernel panic.
PR: 29345
Submitted by: Inoue Yuichi <inoue@nd.net.fujitsu.co.jp>
Obtained from: KAME
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
address was selected.
Reported by: Shingo WATANABE <nabe@nabechan.org>
Submitted by: JINMEI Tatuya <jinmei@isl.rdc.toshiba.co.jp>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bind() call on IPv4 sockets:
Currently, if one tries to bind a socket using INADDR_LOOPBACK inside a
jail, it will fail because prison_ip() does not take this possibility
into account. On the other hand, when one tries to connect(), for
example, to localhost, prison_remote_ip() will silently convert
INADDR_LOOPBACK to the jail's IP address. Therefore, it is desirable to
make bind() to do this implicit conversion as well.
Apart from this, the patch also replaces 0x7f000001 in
prison_remote_ip() to a more correct INADDR_LOOPBACK.
This is a 4.4-RELEASE "during the freeze, thanks" MFC candidate.
Submitted by: Anton Berezin <tobez@FreeBSD.org>
Discussed with at some point: phk
MFC after: 3 days
|
|
|
|
|
|
| |
call.
Obtained from: TrustedBSD Project
|
|
|
|
|
|
| |
Noticed by: fenner
Submitted by: iedowse
Not committed to current by: iedowse ;-)
|
|
|
|
|
|
|
|
| |
as there are now "unusual" protection properties to Pmem that differ
from the other files. While I'm at it, introduce proc locking for
the other files, which was previously present only in the Pmem case.
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
| |
no longer requires access.
Reviewed by: tmm
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and so special-casing was introduced to provide extra procfs privilege
to the kmem group. With the advent of non-setgid kmem ps, this code
is no longer required, and in fact, can is potentially harmful as it
allocates privilege to a gid that is increasingly less meaningful.
Knowledge of specific gid's in kernel is also generally bad precedent,
as the kernel security policy doesn't distinguish gid's specifically,
only uid 0.
This commit removes reference to kmem in procfs, both in terms of
access control decisions, and the applying of gid kmem to the
/proc/*/mem file, simplifying the associated code considerably.
Processes are still permitted to access the mem file based on
the debugging policy, so ps -e still works fine for normal
processes and use.
Reviewed by: tmm
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
| |
particularly nice that IPSEC inserts a zero-length mbuf into the
chain, and that bug should be fixed too, but interfaces should be
robust to bad input.
Print the interface name when TUNDEBUG()ing about dropping an mbuf.
|
|
|
|
|
| |
implementations. More of them seem to be broken, so only "trust"
timers we know work.
|
|
|
|
| |
Submitted by: "neckpain@nettaxi.com" <neckpain@nettaxi.com>
|
|
|
|
| |
Submitted by: "neckpain@nettaxi.com" <neckpain@nettaxi.com>
|
|
|
|
|
|
|
|
| |
order to avoid namespace collision with subr_mchain.c's mb_init(). This
wasn't "fatal" as the mbuf initialization routine mb_init() was local to
subr_mbuf.c which in turn didn't pull in subr_mchain.c's mb_init()
declaration, but it should deffinately be changed now before it creates
headache.
|
|
|
|
|
| |
This is #if BIG_ENDIAN, but is only necessary if malloc types are shorts,
not struct malloc_type * like they are now.
|
|
|
|
| |
the pv module. It works now that vtophys for sttes works.
|
|
|
|
|
|
|
| |
addresses. It helps to use the physical address that the virtual address
actually maps to (doh!). Comment out some code that crashes.
Found independently by: tmm
|
| |
|
|
|
|
|
| |
to build with a cross compiler alongside the standard compiler; it would be
more desirable to build in a chroot.
|
| |
|
| |
|
|
|
|
|
|
| |
commented out in the entire life of the 2.x+ branch and given the amount
of gcc-specific code we have and the warning checks that gcc does I'm not
sure that it is going to get us much for some time.
|
| |
|
| |
|
|
|
|
| |
mi_switch().
|
|
|
|
|
| |
registers later on; this fixes the VIA82C686 sound problems recently
reported by a number of people.
|
|
|
|
|
|
| |
Approved on IRC as long as it didn't cause a large number of warnings by: phk
MFC After: 700 hours
|
|
|
|
|
|
| |
PR: kern/29336
Submitted by: Richard Andrades <richard@xebeo.com>
MFC after: 1 month
|
| |
|
|
|
|
|
| |
#if NSPLASH > 0 (from splash.h) to test the presence
of the splash driver.
|
|
|
|
| |
supported ioctls for now.
|
|
|
|
| |
to video drivers later.
|
|
|
|
|
|
|
|
| |
debugging support as well.
This relies on support added in rev 1.105 to kmod.mk.
Requested by: peter
|
|
|
|
|
|
|
|
| |
to hang or panic kernel by detaching disk from which fs is mounted;
- replace "md" with MD_NAME in yet another place.
Reviewed by: phk
Approved by: phk
|
|
|
|
|
|
|
| |
4 bytes to the right on the alpha.
Tested by: Thomas Pornin <Thomas.Pornin@ens.fr>
MFC after: 1 week
|
|
|
|
|
|
| |
debugging support as well. Debugging module support is handled
identically to kernel debugging support, right down to poor
choice of make variable names.
|
|
|
|
|
|
|
| |
ioctls. We can now add ve, vi and vs capabilities to
cons25 in termcap.
Discussed with and tested by: ache
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) allocate fewer buckets
2) when failing to allocate swap zone, keep reducing the zone by
a third rather than a half in order to reduce the chance of
allocating way too little.
I also moved around some code for readability.
Suggested by: dillon
Reviewed by: dillon
|
|
|
|
|
|
| |
This breaks bogus NVRAM boards.
MFC after: 1 day
|
|
|
|
| |
been hack to keep clocks from being reinitialized.
|
|
|
|
|
|
|
|
|
| |
This paniced my one of my machines one time too many :-( and there is
no sign of a solution in the pipeline. The deltas are still easily
available in cvs. The problem is that if the parent has been swapped
out, the child process cannot grope around in the parent's UPAGES to
see the sigact[] array or it will fault. This probably is a showstopper
for this implementation anyway.
|