mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Wed, 28 May 2003 15:28:27 -0700	[thread overview]
Message-ID: <20030528152827.5387e033.akpm@digeo.com> (raw)
In-Reply-To: <16084.46712.707240.943086@gargle.gargle.HOWL>

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() :)


  parent reply	other threads:[~2003-05-28 22:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  6:43 Milton Miller
2003-05-28 11:14 ` Pavel Machek
2003-05-28 13:15   ` mikpe
2003-05-28 14:18     ` Pavel Machek
2003-05-28 22:28     ` Andrew Morton [this message]
2003-05-28 23:05       ` Pavel Machek
2003-05-28 23:19         ` Nigel Cunningham
2003-05-28 23:36           ` Pavel Machek
2003-05-28 23:10       ` Manfred Spraul
2003-05-29  8:44 ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030528152827.5387e033.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=mikpe@csd.uu.se \
    --cc=miltonm@bga.com \
    --cc=pavel@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®