Date: Mon, 18 Jan 2021 23:21:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 252375] kernel panic during reboot "softdep_waitidle: work added after flush" Message-ID: <bug-252375-227-O1ZruHm71u@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252375-227@https.bugs.freebsd.org/bugzilla/> References: <bug-252375-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252375 --- Comment #2 from Kirk McKusick <mckusick@FreeBSD.org> --- (In reply to Konstantin Belousov from comment #1) I concur with your analysis. The unlocking can allow other operations to ha= ppen 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_wait= idle will simply return EBUSY which can be handled at a higher level. Alternativ= ely 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? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252375-227-O1ZruHm71u>