On Sun, Sep 12, 2010 at 10:02:24PM +0100, Robert Watson wrote:
>
> On Sun, 12 Sep 2010, Kostik Belousov wrote:
>
> >On Sun, Sep 12, 2010 at 09:41:46PM +0100, Robert Watson wrote:
> >>
> >>On Sun, 12 Sep 2010, Konstantin Belousov wrote:
> >>
> >>>Do not fork nfsiod directly from the vop methods. T
On Sun, 12 Sep 2010, Kostik Belousov wrote:
On Sun, Sep 12, 2010 at 09:41:46PM +0100, Robert Watson wrote:
On Sun, 12 Sep 2010, Konstantin Belousov wrote:
Do not fork nfsiod directly from the vop methods. This causes LORs between
vnode lock and several locks needed during fork, like fd lock
On Sun, Sep 12, 2010 at 09:41:46PM +0100, Robert Watson wrote:
>
> On Sun, 12 Sep 2010, Konstantin Belousov wrote:
>
> > Do not fork nfsiod directly from the vop methods. This causes LORs between
> > vnode lock and several locks needed during fork, like fd lock.
> >
> > Instead, schedule the task
On Sun, 12 Sep 2010, Konstantin Belousov wrote:
Do not fork nfsiod directly from the vop methods. This causes LORs between
vnode lock and several locks needed during fork, like fd lock.
Instead, schedule the task to be executed in the taskqueue context. We
still waiting for the fork to fin
Author: kib
Date: Sun Sep 12 19:06:08 2010
New Revision: 212506
URL: http://svn.freebsd.org/changeset/base/212506
Log:
Do not fork nfsiod directly from the vop methods. This causes LORs between
vnode lock and several locks needed during fork, like fd lock.
Instead, schedule the task to be
