linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <f22d86810910220410r33002b5ei403ddf6632254472@mail.gmail.com>
Date:	Thu, 22 Oct 2009 04:10:49 -0700
From:	"Leonidas ." <leonidas137@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Can current macro be accessed from interrupt context?

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?

My use case is to get process id from any context with CONFIG_4KSTACKS = 0 or 1.

Any pointers will be helpful.
-Leo.
--
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/