On Mon, Sep 09, 2024 at 08:16:48AM +0200, Thomas Gleixner wrote: > > From: Roland Xu <mu001999@xxxxxxxxxxx> > > commit d33d26036a0274b472299d7dcdaa5fb34329f91b upstream. > > rt_mutex_handle_deadlock() is called with rt_mutex::wait_lock held. In the > good case it returns with the lock held and in the deadlock case it emits a > warning and goes into an endless scheduling loop with the lock held, which > triggers the 'scheduling in atomic' warning. > > Unlock rt_mutex::wait_lock in the dead lock case before issuing the warning > and dropping into the schedule for ever loop. > > [ tglx: Moved unlock before the WARN(), removed the pointless comment, > massaged changelog, added Fixes tag ] > > Fixes: 3d5c9340d194 ("rtmutex: Handle deadlock detection smarter") > Signed-off-by: Roland Xu <mu001999@xxxxxxxxxxx> > Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > Cc: stable@xxxxxxxxxxxxxxx > Link: https://lore.kernel.org/all/ME0P300MB063599BEF0743B8FA339C2CECC802@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > --- > Backport to 5.10.y, 5.4.y, 4.19.y Now queued up, thanks! greg k-h