From: Sebastian Andrzej Siewior <firstname.lastname@example.org> To: email@example.com Cc: Thomas Gleixner <firstname.lastname@example.org>, Peter Zijlstra <email@example.com>, Ben Skeggs <firstname.lastname@example.org>, Mike Galbraith <email@example.com> Subject: [PATCH 0/2] genirq: Move prio assignment into the newly created thread Date: Tue, 10 Nov 2020 12:38:46 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Mike reported  a lockdep splat triggered by the nouveau driver together with enabled threaded interrupts. I can't easily tell if moving / changing locking within nouveau does not break anything and does not create the same lockchain in another path. Mike did confirm that the lockdep splat can be avoided by by moving `request_irq()' out of the picture . He also tested the two patches which are scattered in the thread. Mike is betting on commit 710da3c8ea7df ("sched/core: Prevent race condition between cpuset and __sched_setscheduler()") as the source change that introduce that problem assuming that locking within the nouveau remained unchanged. He did confirm that this splat exists also in a v5.4 stable kernel  which is where the change was introduced.  https://email@example.com  https://firstname.lastname@example.org  https://email@example.com Sebastian
next reply other threads:[~2020-11-10 11:39 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-10 11:38 Sebastian Andrzej Siewior [this message] 2020-11-10 11:38 ` [PATCH 1/2] kthread: Move prio/affinite change " Sebastian Andrzej Siewior 2020-11-17 12:45 ` Peter Zijlstra 2020-11-20 22:17 ` Sebastian Andrzej Siewior 2020-11-21 10:55 ` Thomas Gleixner 2021-03-03 16:25 ` Sebastian Andrzej Siewior 2020-11-10 11:38 ` [PATCH 2/2] genirq: Move prio assignment " Sebastian Andrzej Siewior
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/2] genirq: Move prio assignment into the newly created thread' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).