https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252375
--- Comment #2 from Kirk McKusick <[email protected]> --- (In reply to Konstantin Belousov from comment #1) I concur with your analysis. The unlocking can allow other operations to happen which could cause new work to show up. My take would be to just delete the KASSERT and let the function loop again. In theory the change could happen more than SU_WAITIDLE_RETRIES (20) times, but even in that scenario softdep_waitidle will simply return EBUSY which can be handled at a higher level. Alternatively we could test for this condition and decrement the loop variable to give it an extra run around the loop, but that seems to be over-thinking the problem. Do you agree with this assessment? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
