Messages in this thread |  | | Date | Sun, 8 Oct 2000 17:08:32 -0600 | From | yodaiken@fsmlabs ... | Subject | Re: Calling current() from interrupt context |
| |
On Mon, Oct 09, 2000 at 01:02:21AM +0200, Jamie Lokier wrote: > yodaiken@fsmlabs.com wrote: > > Looking at the [network] code, I don't see any places where "current" > > is not valid. > > Got some examples? > > Damn I'm being dense tonight. No, that bug was due to calling "current" > from the wrong process context, not from an invalid context. > (Self-flagellate, self-flaggelate).
Don't go overboard here. > > > BTW: there is an implicit reference to "current" in smp_processor_id. > > Yes I forgot about that. (Self-flagellate). However that is > architecture specific. If it's not an SMP Vax port, no big deal. If it
The entire concept of an SMP vax port leaves me disoriented.
-- --------------------------------------------------------- Victor Yodaiken Finite State Machine Labs: The RTLinux Company. www.fsmlabs.com www.rtlinux.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |