linux-kernel - Re: Can current macro be accessed from interrupt context?

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]

Message-ID: <20091022064538.25837421@infradead.org>
Date:	Thu, 22 Oct 2009 06:45:38 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Leonidas ." <leonidas137@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Can current macro be accessed from interrupt context?

On Thu, 22 Oct 2009 04:10:49 -0700
"Leonidas ." <leonidas137@...il.com> wrote:

> Hello,
> 
> Going through UTLK, it says that current macro makes sense only in
> case of process context,
> in case of interrupt context it is invalid.
> 
> But current would still be pointing to interrupted process right? The
> pointer would still be valid?
> Can I safely assume that whether or not interrupt handlers are
> executing on separate stacks or
> interrupted threads stack, current macro can be accessed from
> interrupt context?

not for interrupt threads, and that's where things are moving to.

for interrupt stacks you ought to be fine (current is just a pointer on
the stack, and last I looked we copied that pointer for each interrupt
to the irq stack)

-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/