justanotheruser has quit [Ping timeout: 252 seconds]
<ivan>
Linux 4.19.39 spews new warnings during stage-1-init disk unlocking; WARNING: CPU: 1 PID: 258 at ../kernel/workqueue.c:2911 __flush_work+0x1dc/0x1f0
<gchristensen>
I'm not sure what to say here, I don't understand what is at fault, or what potential solutions might be. maybe try the unhardened kernel?
Synthetica has quit [Quit: Connection closed for inactivity]
<ivan>
gchristensen: same warning with the unhardened kernel, none of my patches applied
<ivan>
whatever I'll just ignore it until upstream carpet-bombs stable with another set of automatically selected patches
<gchristensen>
that does seem to be a uniquely interesting decision, doesn't it?
<samueldr>
though in this case looks like it's a warning intended to eventually fix an issue, hopefully just a warning
<samueldr>
(going from the commit message)
<gchristensen>
I am surprised that they consider automation fit for deciding if things can go back
<samueldr>
hm, and a return false; which is way over my head
<ivan>
samueldr: I assume that's the exception-handling mechanism for if WARN_ON fails
<ivan>
oh probably not
<ivan>
yeah, I guess it doesn't expect to be in that state but gracefully does nothing
<samueldr>
I won't say more since I don't _know_ but it looks like it's short-circuiting a situation that shouldn't happen, where no work would be done anyway