| 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: Thu, 06 Jun 2013 14:33:23 -0700 From: Ben Greear <greearb@...delatech.com> To: Tejun Heo <tj@...nel.org> CC: linux-kernel@...r.kernel.org, eric.dumazet@...il.com Subject: Re: [PATCH v2] Fix lockup related to stop_machine being stuck in __do_softirq. On 06/06/2013 01:48 PM, Tejun Heo wrote: > As wrote before, a brief explanation on why both are necessary would > be nice. Something like - "the time limit prevents from introducing > excessive latency from softirq handling and the loop limit protects > against softirq runaway which may happen during stop_machine - see > XXX". > > Please cc Linus and also cc stable@...r.kernel.org. We definitely > want this backported. v3 was sent, with updated comments and expanded CC list. The patch is against 3.9.4, though I assume it will apply to the upstream kernel easily enough. I didn't want to add a link to the email thread.. The commit message and patch has enough info that I think an interested party could find the email thread easily enough if they needed more history. And, much of the email thread is me running in circles thinking I am going insane :) Thanks, Ben -- Ben Greear <greearb@...delatech.com> Candela Technologies Inc http://www.candelatech.com -- 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