| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 4 Apr 2015 11:34:00 +0200 From: Ingo Molnar <mingo@...nel.org> To: Jesse Brandeburg <jesse.brandeburg@...el.com> Cc: torvalds@...ux-foundation.org, Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org, John <jw@...learfallout.net> Subject: Re: [PATCH] irq: revert non-working patch to affinity defaults * Jesse Brandeburg <jesse.brandeburg@...el.com> wrote: > > Now this is just a small annoyance that should not really matter - > > it would be nice to figure out the real reason for why the irqs > > move back to CPU#0. > > > > In theory the same could happen to 'irqbalanced' as well, if it > > calls shortly after an irq was registered - so this is not a bug > > we want to ignore. > > Let me know if I can do something to help, the IRQ code is a bit of > a steep learning curve, so the chances of me fixing it are small. Well, as a starter, if you can reproduce it on a system (I cannot), then try to stick a few printks in there to print out the affinity mask as it gets changed plus dump_stack(), and see who changes it back? Chances are it's irqbalanced? If not then the stack dump will tell. It shouldn't be too chatty. (trace_printk() if you prefer traces.) Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists