re: panic in -current: "vp->v_iflag & VI_TEXT" failed: file "/usr/src/sys/kern/exec_subr.c", line 183

2022-03-08 Thread matthew green
matthew green writes: > "J. Hannken-Illjes" writes: > > I'm now able to reproduce it here -- takes about six hours to trigger. > > > > I suppose vrelel() lost a check for new references with my last changes, > > currently testing the diff attached. > > well, this ran until i ran out of file

re: panic in -current: "vp->v_iflag & VI_TEXT" failed: file "/usr/src/sys/kern/exec_subr.c", line 183

2022-03-08 Thread matthew green
"J. Hannken-Illjes" writes: > I'm now able to reproduce it here -- takes about six hours to trigger. > > I suppose vrelel() lost a check for new references with my last changes, > currently testing the diff attached. well, this ran until i ran out of file building the native gcc, it had been

Re: panic in -current: "vp->v_iflag & VI_TEXT" failed: file "/usr/src/sys/kern/exec_subr.c", line 183

2022-03-08 Thread J. Hannken-Illjes
> On 8. Mar 2022, at 05:14, matthew green wrote: > > that's this: > > 175 vmcmd_map_pagedvn(struct lwp *l, struct exec_vmcmd *cmd) > 176 { > [ ... ] > 181 vm_prot_t prot, maxprot; > 182 > 183 KASSERT(vp->v_iflag & VI_TEXT); > > christos said this happened to him on a 8c/16t