| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
1. Remove comment stating the blatantly obvious.
2. Align in two columns.
3. Sort all but the default element alphabetically.
4. Remove XXX comments pointing out entries not needed.
|
|
|
|
|
|
|
| |
we freed the name we used to find it..
SO DON'T free it again later!
pointy hat over here please..
|
|
|
|
|
|
|
|
| |
Distribute all but the most fundamental malloc types. This time I also
remembered the trick to making things static: Put "static" in front of
them.
A couple of finer points by: bde
|
|
|
|
| |
Substantial input from: bde
|
|
|
|
| |
filesystems even if not in SPLIT_DEVS mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Clustered I/O is switched by the MNT_NOCLUSTERR and MNT_NOCLUSTERW
bits of the mnt_flag. The sysctl variables, vfs.foo.doclusterread
and vfs.foo.doclusterwrite are deleted. Only mount option can
control clustered I/O from userland.
2. When foofs_mount mounts block device, foofs_mount checks D_CLUSTERR
and D_CLUSTERW bits of the d_flags member in the block device switch
table. If D_NOCLUSTERR / D_NOCLUSTERW are set, MNT_NOCLUSTERR /
MNT_NOCLUSTERW bits will be set. In this case, MNT_NOCLUSTERR and
MNT_NOCLUSTERW cannot be cleared from userland.
3. Vnode driver disables both clustered read and write.
4. Union filesystem disables clutered write.
Reviewed by: bde
|
|
|
|
|
|
|
|
| |
plus the previous changes to use the zone allocator decrease the useage
of malloc by half. The Zone allocator will be upgradeable to be able
to use per CPU-pools, and has more intelligent usage of SPLs. Additionally,
it has reasonable stats gathering capabilities, while making most calls
inline.
|
|
|
|
|
|
|
| |
a trap.
PR: 3104
Reviewed by: phk
Submitted by: Dan Walters hannibal@cyberstation.net
|
|
|
|
| |
I'm going to try migrate back, while keeping the newer code.
|
|
|
|
|
| |
Delete 'always succeed' select/poll handlers, replaced with generic call.
Flag missing vnode op table entries.
|
|
|
|
| |
cleaned up nearby cruft.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fixes problems in unmounting and propogation.
|
|
|
|
|
| |
Remove all traces of the name_cache from devfs. It is hardly sensible to
use the namecache for an all-RAM filesystem.
|
|
|
|
|
|
|
|
| |
socket addresses in mbufs. (Socket buffers are the one exception.) A number
of kernel APIs needed to get fixed in order to make this happen. Also,
fix three protocol families which kept PCBs in mbufs to not malloc them
instead. Delete some old compatibility cruft while we're at it, and add
some new routines in the in_cksum family.
|
|
|
|
|
|
| |
points `.'.
Obtained from: NetBSD
|
| |
|
|
|
|
|
|
| |
a file to upper layer.
Reviewed by: Naofumi Honda <honda@Kururu.math.sci.hokudai.ac.jp>
|
|
|
|
| |
manpage works again.
|
|
|
|
|
|
|
|
|
|
|
| |
uerror == 0 && lerror == EACCES, lowervp == NULLVP and union_allocvp
doesn't find existing union node and new union node is created.
Sicne it is dificult to cover all the case, union_lookup always
returns when union_lookup1() returns EACCES.
Submitted by: Naofumi Honda <honda@Kururu.math.sci.hokudai.ac.jp>
Obtained from: NetBSD/pc98
|
| |
|
|
|
|
|
|
|
| |
reading/writing of mem and regs). Also have to check for the requesting
process being group KMEM -- this is a bit of a hack, but ps et al need it.
Reviewed by: davidg
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The additional check in procfs_ctl.c could be backed out, but
I'm leaving it in for good measure.
Reviewed by: Theo de Raadt <deraadt@OpenBSD.org>
|
|
|
|
| |
cleaned. This should help for PR kern/3581.
|
|
|
|
| |
umapfs uses one of nullfs's functions...
|
|
|
|
|
|
|
| |
union_statfs().
2. staticized union vops.
Submitted by: Doug Rabson <dfr@nlsystems.com>
|
|
|
|
|
| |
PR: 3276 & 3469 (the fixes), 2738, 2033 (reports)
Submitted by: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
|
| |
|
|
|
|
|
|
| |
in savedvp variable and it is used for the argument of
MOUNTTOUNIONMOUNT(). I didn't realize ap->a_vp is modified before
MOUNTTOUNIONMOUNT(), so the change by revision 1.22 is incorrect.
|
|
|
|
|
| |
sector devices given that the fs uses a blocksize of at least a physical
sector size.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
UN_KLOCK flag.
When UN_KLOCK is set, VOP_UNLOCK should keep uppervp locked and clear
UN_ULOCK flag. To do this, when UN_KLOCK is set, (1) union_unlock
clears UN_ULOCK and does not clear UN_KLOCK, (2) union_lock() does not
access uppervp and does not clear UN_KLOCK, and (3) callers of
vput/VOP_UNLOCK should clear UN_KLOCK. For example, vput becomes:
SETKLOCK(union_node);
vput(vnode);
CLEARKLOCK(union_node);
where SETKLOCK macro sets UN_KLOCK and CLEARKLOCK macro clears
UN_KLOCK.
|
| |
|
|
|
|
| |
Noticed by: Brian Buchanan <brian@wasteland.calbbs.com>
|
| |
|
|
|
|
|
| |
(UN_ULOCK is not set) in union_lock. This condition may indicate
race. DIAGNOSTIC kernel still panic here.
|
|
|
|
|
|
|
|
|
| |
Our vput calls vm_object_deallocate() --> vm_object_terminate(). The
vm_object_terminate() calls vn_lock(), since UN_LOCKED has been
already cleared in union_unlock(). Then, union_lock locks upper vnode
when UN_ULOCK is not set. The upper vnode is not unlocked when
UN_KLOCK is set in union_unlock(), thus, union_lock tries to lock
locked vnode and we get panic.
|
|
|
|
|
|
|
|
| |
UN_ULOCK flag. This shows a locking violation but I couldn't find the
reason UN_ULOCK is not set or upper vnode is not unlocked. I added
the code that detect this case and adjust un_flags. DIAGNOSTIC kernel
doesn't adjust un_flags, but just panic here to help debug by kernel
hackers.
|