[lkml]   [2000]   [Oct]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Calling current() from interrupt context
On Mon, Oct 09, 2000 at 01:02:21AM +0200, Jamie Lokier wrote:
> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:39    [W:0.355 / U:0.744 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site