Displaying 8 results from an estimated 8 matches for "v_type".
Did you mean:
d_type
1999 Sep 03
0
FreeBSD-SA-99:01: BSD File Flags and Programming Techniques
...+ * Prevent non-root users from setting flags on devices. When
+ * a device is reused, users can retain ownership of the device
+ * if they are allowed to set flags and programs assume that
+ * chown can't fail when done as root.
+ */
+ if ((vp->v_type == VCHR || vp->v_type == VBLK) &&
+ ((error = suser_xxx(p->p_ucred, p, PRISON_ROOT)) != 0))
+ return (error);
+
VOP_LEASE(vp, p, p->p_ucred, LEASE_WRITE);
vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p);
VATTR_NU...
1998 Mar 12
2
FreeBSD Security Advisory: FreeBSD-SA-98:02.mmap
...* memory via /dev/mem, it should never work at any
+ * other securelevel.
+ * XXX this will have to go
+ */
+ if (securelevel >= 1)
+ disablexworkaround = 1;
+ else
+ disablexworkaround = suser(p->p_ucred,
+ &p->p_acflag);
+ if (vp->v_type == VCHR && disablexworkaround &&
+ (flags & (MAP_PRIVATE|MAP_COPY)))
+ return (EINVAL);
+ /*
* Ensure that file and memory protections are
* compatible. Note that we only worry about
* writability if mapping is shared; in this case,
@@ -265...
2003 Jun 11
1
nfs panic with umount -f
...= {tqe_next = 0x0,
tqe_prev = 0xe80bc75c}, v_nmntvnodes = {tqe_next = 0xe8468b40,
tqe_prev = 0xc23a7418}, v_cleanblkhd = {tqh_first = 0x0,
tqh_last = 0xe8469cac}, v_dirtyblkhd = {tqh_first = 0x0,
tqh_last = 0xe8469cb4}, v_synclist = {le_next = 0x0, le_prev = 0x0},
v_numoutput = 0, v_type = VBAD, v_un = {vu_mountedhere = 0x0,
vu_socket = 0x0, vu_spec = {vu_specinfo = 0x0, vu_specnext = {
sle_next = 0x0}}, vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0,
v_cstart = 0, v_lasta = 0, v_clen = 0, v_object = 0x0, v_interlock = {
lock_data = 0}, v_vnlock = 0x0, v_tag = VT_...
2003 May 16
3
open and euid security flaw in 5.0-Current?
On a FreeBSD 5.0 the behaviour of screen when connecting to other
users sessions have changed. Previously:
1. login as userA start a screen as userA and disconnect
2. login as root su - userA "screen -r"
3. result failure as userA cant access the ttyX with such a message
Current:
1. login as userA start a screen as userA and disconnect
2. login as root su - userA "screen -r"
3.
2003 Jul 02
0
union_lookup panics ...
...tqe_next = 0x0, tqe_prev = 0xc187151c}, v_nmntvnodes = {
tqe_next = 0xc2cdeec0, tqe_prev = 0xbfefe264}, v_cleanblkhd = {
tqh_first = 0x0, tqh_last = 0xc5e062ec}, v_dirtyblkhd = {tqh_first =
0x0,
tqh_last = 0xc5e062f4}, v_synclist = {le_next = 0x0, le_prev = 0x0},
v_numoutput = 0, v_type = VREG, v_un = {vu_mountedhere = 0x0,
vu_socket = 0x0, vu_spec = {vu_specinfo = 0x0, vu_specnext = {
sle_next = 0x0}}, vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0,
v_cstart = 0, v_lasta = 0, v_clen = 0, v_object = 0x0, v_interlock = {
lock_data = 0}, v_vnlock = 0x0, v_tag = VT_...
2003 Aug 19
0
inode deadlock: can't reclaim VLRU: suggestions please [was RE: k ernel deadlock]
...process to
signal that vnodes are available (10% of the vnodes need to be
freed).
Under our test, none of the nodes meet the criteria for freeing,
so the vnlru process goes to sleep for 3 seconds without signaling
anything. Then it wakes, tries again, same result.
Current constraints are:
- v_type is not VNON or VBAD
- v_object is NULL or v_object->resident_page_count < trigger
- VMIGHTFREE(vp) is true
- can acquire vp->v_interlock
I tried adding code which uses only the following constraints if
no nodes could be freed the previous time:
- VMIGHTFREE(vp) is true
- can acqui...
2007 May 09
5
Refactor zfs_zget()
Hi,
Since almost all operations in the FUSE low-level API identify files by inode
number, I''ve been using zfs_zget() to get the corresponding znode/vnode in
order to call the corresponding VFS function in zfs_vnops.c.
However, there are some cases when zfs_zget() behaves slightly different than
I need:
1) If zp->z_unlinked != 0 then zfs_zget() returns ENOENT. I need it to return
2006 Nov 17
1
gjournal on 6.x wont build
Hi all,
I was intending on trying out gjournal on a new disk i've added in my
desktop. I had a look to see what the most recent patch provided by
Pawel and found
http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch
I created the directories as per Pawel's original post
(http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html)
and the patch succeeded with no failed