search for: v_flag

...et_t)vmaddr); file_addr = trunc_page(offset); @@ -341,6 +356,12 @@ } error = exec_map_first_page(imgp); + /* + * Also make certain that the interpreter stays the same, so set + * its VTEXT flag, too. + */ + if (error == 0) + nd.ni_vp->v_flag |= VTEXT; VOP_UNLOCK(nd.ni_vp, 0, p); if (error) goto fail; @@ -449,6 +470,17 @@ /* * From this point on, we may have resources that need to be freed. */ + + /* + * Yeah, I'm paranoid. There is every reason in the world to g...

...; in between the command and the filename. This patch fixed the problem. /mjt exec.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletion(-) --- ash/exec.c.orig Thu Sep 16 01:36:58 2004 +++ ash/exec.c Sat Nov 13 02:22:02 2004 @@ -1031,8 +1031,10 @@ typecmd(int argc, char **argv) if (!v_flag) out1fmt(" is%s ", cmdp ? " a tracked alias for" : ""); -#endif out1fmt("%s\n", name); +#else + out1fmt(" is %s\n", name); +#endif } else { if (access(arg, X_OK) == 0) { if (!v_flag)

...panic("union_lookup returning . (%p) not same as startdir (%p)", ap->a_vpp, dvp); 616 } 617 #endif 618 619 return (error); (kgdb) print *ap->a_vpp $1 = (struct vnode *) 0x0 (kgdb) print dvp $2 = (struct vnode *) 0xc5e062c0 (kgdb) print *dvp $3 = {v_flag = 0, v_usecount = 1, v_writecount = 0, v_holdcnt = 0, v_id = 272969383, v_mount = 0x89a7dc00, v_op = 0x89475000, v_freelist = { tqe_next = 0x0, tqe_prev = 0xc187151c}, v_nmntvnodes = { tqe_next = 0xc2cdeec0, tqe_prev = 0xbfefe264}, v_cleanblkhd = { tqh_first = 0x0, tqh_last = 0xc5e062...

...VMIGHTFREE(vp) is true - can acquire v_interlock However, few nodes meet these constraints either. Which of the following approaches seem best: 1. Can I do away with some of the VMIGHTFREE() criteria? I.e., are they constraints or merely heuristics? #define VMIGHTFREE(vp) \ (!((vp)->v_flag & (VFREE|VDOOMED|VXLOCK)) && \ LIST_EMPTY(&(vp)->v_cache_src) && !(vp)->v_usecount) 2. If there is a dependancy on one of the user processes, can I determine the offendor (maybe kill it)? 3. Should vnlru process signal the requestor if as few as one node...

Is it possible to use DTrace to display the number of arguments and their types for userland or kernel functions that are not explicitly instrumented or documented by their authors? We''re talking about functions provided by Veritas VxVM/VxFS and the like, and for example, we might want to try tracing I/Os from App => VxFS => VxVM => ssd driver to see where I/Os get aggregated or

...b2; 1582 int v3 = NFS_ISV3(dvp); 1583 1584 nfsstats.rpccnt[NFSPROC_REMOVE]++; 1585 nfsm_reqhead(dvp, NFSPROC_REMOVE, 1586 NFSX_FH(v3) + NFSX_UNSIGNED + nfsm_rndup(namelen)); (kgdb) p *proc Cannot access memory at address 0x0. (kgdb) p *dvp $3 = {v_flag = 0, v_usecount = 9, v_writecount = 0, v_holdcnt = 0, v_id = 4278, v_mount = 0x0, v_op = 0xc223e700, v_freelist = {tqe_next = 0x0, tqe_prev = 0xe80bc75c}, v_nmntvnodes = {tqe_next = 0xe8468b40, tqe_prev = 0xc23a7418}, v_cleanblkhd = {tqh_first = 0x0, tqh_last = 0xe8469cac}, v_dirtyblk...