Date: Wed, 28 May 2003 15:28:27 -0700
From: Andrew Morton <akpm@digeo.com>
To: mikpe@csd.uu.se
Cc: pavel@suse.cz, miltonm@bga.com, linux-kernel@vger.kernel.org,
       Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [PATCH] fix oops on resume from apm bios initiated suspend
Message-Id: <20030528152827.5387e033.akpm@digeo.com>
In-Reply-To: <16084.46712.707240.943086@gargle.gargle.HOWL>
References: <200305280643.h4S6hRQF028038@sullivan.realtime.net>
	<20030528111401.GB342@elf.ucw.cz>
	<16084.46712.707240.943086@gargle.gargle.HOWL>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 924
Lines: 24

mikpe@csd.uu.se wrote:
>
>  > > -	load_LDT(&current->mm->context);	/* This does lldt */
>  > > +	load_LDT(&current->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(&current->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/