On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote:
> > > Index: vfs_aio.c
> > > ===================================================================
> > > --- vfs_aio.c (revision 305811)
> > > +++ vfs_aio.c (working copy)
> > > @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *job)
> > > * aio_aqueue() acquires a reference to the file that is
> > > * released in aio_free_entry().
> > > */
> > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace,
> > > + ("%s: vmspace mismatch", __func__));
> > > if (cb->aio_lio_opcode == LIO_READ) {
> > > auio.uio_rw = UIO_READ;
> > > if (auio.uio_resid == 0)
> > > @@ -1054,6 +1056,8 @@ aio_switch_vmspace(struct kaiocb *job)
> > > {
> > >
> > > vmspace_switch_aio(job->userproc->p_vmspace);
> > > + KASSERT(curproc->p_vmspace == job->userproc->p_vmspace,
> > > + ("%s: vmspace mismatch", __func__));
> > > }
> > >
> > > If this panics, then vmspace_switch_aio() is not working for
> > > some reason.
> >
> > This issuse caused rare, this panic produced with issuse or on any aio
> > request? (this is production server)
>
> It would panic in the case that we are going to write into the wrong
> process (so about as rare as your issue).
Can I configure automatic reboot (not halted) in this case?
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
