kib a6f1fd882b When non-forced unmount or remount rw->ro is performed, writes on UFS ... are not suspended. In particular, on the SU-enabled vulumes, there is no reason why, between the call to softdep_flushfiles() and softdep_waitidle(), SU work items cannot be queued. Correct the condition to trigger the panic by only checking when forced operation is done. Convert direct panic() call into KASSERT(), there is no invalid on-disk data structures directly involved, so follow the usual debugging vs. non-debugging approach. Reported and tested by: pho Reviewed by: mckusick Sponsored by: The FreeBSD Foundation MFC after: 1 week		2014-11-02 13:14:55 +00:00
..
ffs	When non-forced unmount or remount rw->ro is performed, writes on UFS	2014-11-02 13:14:55 +00:00
ufs	Use lockless quota checks in qsync and qsyncvp.	2014-10-16 12:41:14 +00:00