| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Discussed with: imp
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of having the kernel parse that line and add an entry to the argument list for
each 'separate word' it finds, have it add only one entry which holds all
the words found on that line. The old behavior is useful in some situations,
but it does not match the way any other operating system will parse that line.
This has been discussed in the thread "Bug in #! processing - One More Time"
on the freebsd-arch mailing list (starting back on Feb 24, 2005). The first
few messages in that thread provide the background in much detail.
PR: 16393
Reviewed by: freebsd-arch
|
|
|
|
|
|
|
| |
PR: kern/48759
Submitted by: Pawe³ Ma³achowski <pawmal@unia.3lo.lublin.pl>
Patch from: demon
MFC after: 2 weeks
|
|
|
|
| |
Reviewed by: bms
|
|
|
|
| |
synchronization.
|
|
|
|
|
|
| |
releasing it in pmap_enter_quick().
MFC after: 3 weeks
|
| |
|
| |
|
|
|
|
| |
Giant if required.
|
|
|
|
|
|
|
| |
sysctl path. While this code is close to MPSAFE, it may require some
additional locking. Mark ntp_gettime1() as GIANT_REQUIRED for now.
Suggested by: phk
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on the their simply wrapping MPSAFE implementations of existing MPSAFE
system calls:
getfsstat()
lseek()
stat()
lstat()
truncate()
ftruncate()
statfs()
fstatfs()
Note that ogetdirentries() is not marked MPSAFE because it does not share
the MPSAFE implementation used for getdirentries(), and requires separate
locking to be implemented.
|
|
|
|
|
|
|
|
|
| |
Note: len gets intialized to 0 for sap == NULL case only to
make compiler on amd64 happy. This has nothing todo with the
former uninitialized use of len in sap != NULL case.
Reviewed by: glebius
Approved by: pjd (mentor)
|
| |
|
| |
|
|
|
|
| |
entry can become MSTD.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
acquire Giant themselves.
|
|
|
|
|
| |
so that we can start to eliminate the presence of non-MPSAFE system
call entries in syscalls.master.
|
| |
|
|
|
|
|
|
| |
PR: kern/81573
Submitted by: OOTOMO Hiroyuki <ootomo@za.wakwak.com>
MFC after: 1 week
|
|
|
|
| |
desirable, though.
|
|
|
|
| |
instead of a dead location on ftp.isi.edu.
|
|
|
|
|
|
|
| |
(where I incorrectly put it initially) to "ignored" devices list (where
it should be). Pointy hat goes to me.
MFC after: 3 days
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Teach the i386 and pc98 loaders to honor multiple console requests from
their respective boot2 binaries so that the same console(s) are used in
both boot2 and the loader.
- Since the kernel doesn't support multiple consoles, whichever console is
listed first is treated as the "primary" console and is passed to the
kernel in the boot_howto flags.
PR: kern/66425
Submitted by: Gavin Atkinson gavin at ury dot york dot ac dot uk
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
output is sent to the correct console(s).
PR: kern/66425
Submitted by: Gavin Atkinson gavin at ury dot york dot ac dot uk
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
Giant is probably also needed in kern_fhstatfs().
|
| |
|
|
|
|
|
|
| |
128-bit UUID libsdp(3). Fix 128-bit UUID printing in sdpcontrol(8).
MFC after: 3 days
|
|
|
|
| |
only for backward compatibility since 5.2-RELEASE.
|
|
|
|
|
| |
statistics, not graph and statistical test output. Useful for automated
processing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that protects socket and receive socket buffer state, and a second
mutex to protect send socket buffer state. In some places, the
mutex shared between the socket and receive socket buffer will be
acquired twice, once by each layer, resulting in some
inconsistency, but providing the abstraction benefit of being able
to more easily separate the two mutexes in the future if desired.
When transitioning a socket to the SS_ISDISCONNECTING or
SS_ISDISCONNECTED states, grab the socket/receive socket buffer lock
once rather than grabbing it as the socket lock, modifying socket
state, then grabbing a second time as the receive lock in order to
modify the socket buffer state to indicate no further data can be
read. This change is believed to close a race between the change in
socket state and the change in socket buffer state, which for a
remotely initiated close on a UNIX domain socket, resulted in
soreceive() returning ENOTCONN rather than an EOF condition.
A similar race still exists in the case of send, however, and is
harder to fix as the socket and send socket buffer mutexes are not
the same, and we would like to avoid holding combinations of socket
mutexes over sb_upcall until we've finished clarifying the locking
protocol for upcalls.
This change has the side affect of reducing the number of mutex
operations to initiate disconnect or perform disconnect on a
socket by two.
PR: 78824
Rerported by: Marc Olzheim <marcolz@stack.nl>
MFC after: 2 weeks
|
|
|
|
|
| |
day's sleep queue code, today the bug no longer exists.
please see 04/25/2004 freebsd-threads@ mailing list archive.
|
|
|
|
|
|
|
|
|
| |
and RAND_MAX != LONG_MAX on 64-bit platforms.
PR: amd64/81279
Submitted by: Vivek Khera vivek at khera dot org
Submitted by: Adriaan de Groot groot at kde dot org
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the ipx_net data structure. Doing so introduced a stronger alignment
requirement for the address structure, which in turn propagated into
other dependent data structures, which turns out not to be suported by
the available IPX source code. As a result, a number of user space
applications, such as IPX routing components, failed to operate
correctly.
RELENG_5_3 candidate?
PRs: 74059, 80266
Pointy hat to: bms
Fix by: bde
Tested by: Keith White <Keith dot White at site dot uottawa dot ca>
MFC after: 1 week
Suffering: great
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
long (and unsigned long long) to long double conversions.
- Add a parameter that specifies the position of the sign bit to the _QP_TTOQ
macro, previously it always looked at bit 31. Pass a negative number to
disable sign inspection for unsigned types. This fixes _Qp_xtoq(),
_Qp_uitoq() and _Qp_uxtoq().
- In the functions __fpu_itof() and __fpu_xtof(), look at the sign bit to
decide whether we're doing a conversion from an unsigned type. If so, don't
negate the mantissa if the integer exceeds the biggest signed number.
PR: 55773
Patch by: Stephen Paskaluk (based upon)
MFC after: 2 weeks
|
|
|
|
|
|
| |
thus being compatible with both XFree86 and X.org.
Noticed by: danfe
|
| |
|
|
|
|
|
|
| |
Actually, it causes process to hang when it is being debugged.
PR: gnu/77818
|
|
|
|
| |
/boot/kernel/kernel, not plain /kernel
|
| |
|
|
|
|
| |
noughties, not eighties.
|