Messages in this thread |  | | Date | Wed, 28 May 2003 15:28:27 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH] fix oops on resume from apm bios initiated suspend |
| |
mikpe@csd.uu.se wrote: > > > > - load_LDT(¤t->mm->context); /* This does lldt */ > > > + load_LDT(¤t->active_mm->context); /* This does lldt */ > > No one has still explained WHY kapmd's current->mm is NULL for some people, > while it obviously is non-NULL for many others.
All kernel threads have current->mm = NULL, via daemonize()->exit_mm(). So the question becomes "why does this code get called by kernel threads for some people, and not for others"? Pavel?
Also, is there any point in doing load_LDT(¤t->active_mm->context) for a kernel thread?
> That worries me a lot more.
I'm more worried by the 113-column line in fix_processor_context() :)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |