linux-kernel - Re: stack overflow on Sparc64

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Jun 2008 14:20:34 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mpatocka@...hat.com
Cc:	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org,
	agk@...hat.com
Subject: Re: stack overflow on Sparc64

From: Mikulas Patocka <mpatocka@...hat.com>
Date: Fri, 20 Jun 2008 17:14:41 -0400 (EDT)

> Are you sure? What about this:
> ide-io.c:ide_intr
>          if (drive->unmask)
>                  local_irq_enable_in_hardirq();
> 
> or this:
> kernel/irq/handle.c:handle_IRQ_event
>          if (!(action->flags & IRQF_DISABLED))
>                  local_irq_enable_in_hardirq();
> 
> 
> --- how is number of nested interrupts here supposed to be limited?
> 
> If these things are not limited, you get at most as many nested handlers 
> as there are hardware interrupts, which means crash.

It means i386 and every other platform potentially has the same exact
problem.

What point wrt. sparc64 are you trying to make here? :-)


--
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/