| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
confuses the controller, tell CAM not to do it. Also report the
correct error condition to CAM when it tries to probe a target that
doesn't exists.
This should make the CAM interface less risky to use.
MFC After: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dereferenced when a process exits due to the vmspace ref-count being
bumped. Change shmexit() and shmexit_myhook() to take a vmspace instead
of a process and call it in vmspace_dofree(). This way if it is missed
in exit1()'s early-resource-free it will still be caught when the zombie is
reaped.
Also fix a potential race in shmexit_myhook() by NULLing out
vmspace->vm_shm prior to calling shm_delete_mapping() and free().
MFC after: 7 days
|
|
|
|
|
|
| |
routine really need to be gutted and merged with exit1().
Reviewed by: jhb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
access its controlling terminal.
In essense, history dictates that any process is allowed to open
/dev/tty for RW, irrespective of credential, because by definition
it is it's own controlling terminal.
Before DEVFS we relied on a hacky half-device thing (kern/tty_tty.c)
which did the magic deep down at device level, which at best was
disgusting from an architectural point of view.
My first shot at this was to use the cloning mechanism to simply
give people the right tty when they ask for /dev/tty, that's why
you get this, slightly counter intuitive result:
syv# ls -l /dev/tty `tty`
crw--w---- 1 u1 tty 5, 0 Jan 13 22:14 /dev/tty
crw--w---- 1 u1 tty 5, 0 Jan 13 22:14 /dev/ttyp0
Trouble is, when user u1 su(1)'s to user u2, he cannot open
/dev/ttyp0 anymore because he doesn't have permission to do so.
The above fix allows him to do that.
The interesting side effect is that one was previously only able
to access the controlling tty by indirection:
date > /dev/tty
but not by name:
date > `tty`
This is now possible, and that feels a lot more like DTRT.
PR: 46635
MFC candidate: could be.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Revision 1.38 introduced the -n flag. It conflicted with the
RB_BOOTINFO flag, so was in effect always on. Change the -n flag to
be bit 0x1c instead of 0x1f. This also had the consequence that a mal-formed
/boot.config would render the system unbootable because the user was
unable to enter anything at all on the command line.
o Remove the initialization of opt to be RB_BOOTINFO since we filter that bit
out and do not otherwise use it.
Reviewed by: jhb
MFC after: 3 days
|
|
|
|
| |
Stumbled on by: bde
|
|
|
|
|
| |
Submitted by: "Mikko S. Hyvarinen" <morphy@morphy.iki.fi>
MFC after: 5 days
|
|
|
|
|
| |
Submitted by: "Mikko S. Hyvarinen" <morphy@morphy.iki.fi>
MFC after: 5 days
|
|
|
|
| |
driver a _real_ GEOM driver.
|
|
|
|
|
|
|
|
|
| |
- Don't panic on contigmalloc failure.
- Calculate timestamp by feedforward rather than feedback which depends on
unreliable interrupt timing.
- Overwrite timestamp in CIP header correctly.
- Add debug code for timestamp synchronization.
- Add comments.
|
|
|
|
| |
Fill fdf bit fields and others.
|
| |
|
|
|
|
|
|
|
| |
ioctls are no reliable indication of the ioctls "set" or "get" nature or if
such simplistic categories can even be applied.
MFC candidate: boot0cfg issue.
|
|
|
|
| |
Reviewed by: Tom Henderson <thomas.r.henderson@boeing.com>
|
|
|
|
|
|
|
|
| |
Only grab giant in the per unit kthread for SWAP and VNODE backed devices.
Initialize the bioq before the kthread gets a chance to study it.
Don't lock Giant in mddone_swap, we shouldn't need it.
|
|
|
|
|
|
|
| |
out since rev 1.1 (24 may 1994) of this file.
Add a nail to the K&R coffin by removing the #ifdef'ed K&R function
declaration for NDINIT.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
inconsistent when we do not do it for swap or vnode.
We still printf for preloaded disks because of the weak debugging
options people have in embedded/tiny environments where this is
usually used.
|
|
|
|
| |
Submitted by: Toru Morimoto <too@os.gulf.or.jp>
|
|
|
|
|
|
| |
PR: kern/46386
Submitted by: dillon
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
| |
to access the pctcpu. This will have to be sorted out more later as the
new scheduler requires a procedural interface for this data. A more
complete solution will follow.
|
|
|
|
| |
resources we're managing.
|
|
|
|
|
| |
removal of unnecessary casts and throw in some minor cleanups to see if
anyone complains, just for the hell of it.
|
|
|
|
|
|
|
|
|
|
| |
The objective being to eliminate some cases of page queues locking.
(See, for example, vm/vm_fault.c revision 1.160.)
Reviewed by: tegge
(Also, pointed out by tegge that I changed vm_fault.c before changing
vm_page.c. Oops.)
|
|
|
|
|
|
| |
the disk mini-layer.
This is currently not enabled.
|
|
|
|
|
|
|
| |
and 3com MAC. Specifications for the Altima PHY are available at:
http://www.altimacom.com/products/ac101L.html
Submitted by: Mikko S. Hyvarinen <morphy@morphy.iki.fi>
|
|
|
|
|
| |
This will prevent access through mechanisms other than the published
interfaces.
|
| |
|
|
|
|
| |
trouble. Return EINVAL instead.
|
| |
|
| |
|
|
|
|
| |
VM_ALLOC_ZERO to vm_page_alloc().
|
|
|
|
| |
VM_ALLOC_ZERO to vm_page_alloc(). (PG_ZERO is clear by default.)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
pointer types, and remove a huge number of casts from code using it.
Change struct xfile xf_data to xun_data (ABI is still compatible).
If we need to add a #define for f_data and xf_data we can, but I don't
think it will be necessary. There are no operational changes in this
commit.
|
|
|
|
|
|
|
|
|
|
| |
expectation.
This solves the problem, where in a constellation with two (or more)
drives, an attempt is made to access a device name for that device
using a historic partition letter, like /dev/fd1c. This is supposed
to create a symlink to the master device, but previously, the link was
always created to /dev/fd0, even if the request was for fd1*.
|
|
|
|
|
|
| |
PR: 41466
Submitted by: NIIMI Satoshi <sa2c@sa2c.net>
MFC after: 1 week
|
|
|
|
| |
expression.
|
| |
|
| |
|
|
|
|
| |
RATOC REX-9530 is SCSI2 Card.
|
| |
|
|
|
|
| |
same product id. So use CIS info(PCCARD_CISTPL_VERS_1).
|
|
|
|
| |
Pointy hats to: dillon, Hiten Pandya <hiten@unixdaemons.com>
|