Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261790AbTESVzG (ORCPT ); Mon, 19 May 2003 17:55:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263025AbTESVzG (ORCPT ); Mon, 19 May 2003 17:55:06 -0400 Received: from modemcable204.207-203-24.mtl.mc.videotron.ca ([24.203.207.204]:30592 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id S261790AbTESVzF (ORCPT ); Mon, 19 May 2003 17:55:05 -0400 Date: Mon, 19 May 2003 17:57:48 -0400 (EDT) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: mikpe@csd.uu.se cc: alexander.riesen@synopsys.COM, "" , "" , "" Subject: Re: 2.5.69+bk: oops in apmd after waking up from suspend mode In-Reply-To: <200305191216.h4JCGONj015081@harpo.it.uu.se> Message-ID: References: <200305191216.h4JCGONj015081@harpo.it.uu.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 603 Lines: 17 On Mon, 19 May 2003 mikpe@csd.uu.se wrote: > As to _why_ kapmd's current->mm is NULL, I don't know. It isn't > when I test APM suspend in 2.5.69-bk. A lot of code dereferences > current->mm without checking, so I guess current->mm==NULL is a bug. For kernel threads (as is the case with kapmd) current->mm would be NULL. Zwane -- function.linuxpower.ca - 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/