linux-kernel - Re: DEBUG_STACKOVERFLOW issue on ARM

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20121011080108.GL4625@n2100.arm.linux.org.uk>
Date:	Thu, 11 Oct 2012 09:01:08 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	vaibhav shinde <v.bhav.shinde@...il.com>
Cc:	trisha yad <trisha1march@...il.com>, linux-kernel@...r.kernel.org,
	Ralf Baechle <ralf@...ux-mips.org>
Subject: Re: DEBUG_STACKOVERFLOW issue on ARM

On Thu, Oct 11, 2012 at 01:09:46PM +0530, vaibhav shinde wrote:
> Hi Russel,
> 
> On Fri, Oct 5, 2012 at 2:01 PM, Russell King - ARM Linux
> <linux@....linux.org.uk> wrote:
> >
> > On Wed, Oct 03, 2012 at 05:18:56PM +0530, trisha yad wrote:
> > > I wish to know how can I support this function in 3.0 ?
> >
> > If your description is correct, then all you need to do is to ensure
> > that you route interrupts to other CPUs.
> >
> > You can do that by running the userspace irqbalance daemon.
> >
> 
> I also tried with the irqbalance daemon, on ARM quad core architecture,
> and as per my understanding, the daemon sets the
> /proc/irq/<irq.no.>/smp_affinity
> file according to the irq frequency on a particular processor.
> 
>           However, the daemon doesn't work as expected, I also tried
> accessing the
> proc file mentioned above to set the cpu mask for particular irq, but this
> just block the processing of the irq, as I see the count of that irq
> doesnt increase
> in /proc/interrupts.
> 
>             My conclusion is that the irqbalancing is not supported on
> ARM arch or there is
> something  more required for this to work. Kindly provide some
> pointers over this.

Sounds like something has been broken, no idea what.  It needs investigation.
--
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/