On Tue, May 05, 2015 at 11:02 -0700, Philip Guenther wrote:
> On Tue, May 5, 2015 at 9:35 AM, Mike Belopuhov wrote:
> ...
> > Here's a diff to remedy this. This is the same chunk as in the
> > tsleep, except it uses semantics of msleep. IPL dance is there
> > to negate the IPL changing effect of
On Tue, May 05, 2015 at 11:02 -0700, Philip Guenther wrote:
> On Tue, May 5, 2015 at 9:35 AM, Mike Belopuhov wrote:
> ...
> > Here's a diff to remedy this. This is the same chunk as in the
> > tsleep, except it uses semantics of msleep. IPL dance is there
> > to negate the IPL changing effect of
On Tue, May 5, 2015 at 9:35 AM, Mike Belopuhov wrote:
...
> Here's a diff to remedy this. This is the same chunk as in the
> tsleep, except it uses semantics of msleep. IPL dance is there
> to negate the IPL changing effect of mtx_enter/mtx_leave so that
> splx(safepri) operation is actually cha
Now that we have mutexes in our I/O path (SCSI, mfi, etc)
vfs_shutdown codepath is no longer safe since it still doesn't
disable process scheduling and relies on tsleep and now msleep
not to get into the mi_switch by accident. Unfortunately msleep
doesn't provide such guarantees yet.
Here's a dif
