From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: current->mm
Date: Thu, 6 Jun 2002 12:25:48 +0200 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJIEFMCFAA.Stephan.Linke@epygi.de> (raw)
Hi!
I'm running a 2.4.18 kernel on a 862/857 board.
In some codes related to pag allocation there's a myterious problem where
current->mm is zero.
I don't know anything about current current->mm except that it may be the
memory list of the current contex. But I think it should not be zero after a
page was allocated...
Any know issues in that direction?
Thanks 4 ur help, Stephan
#--
STEPHAN LINKE (dipl. inform); software engineer
epygi labs de gmbh; herrenstraße 23, 3. og, D-76133 karlsruhe
http://www.epygi.de; mailto:stephan.linke@epygi.de
phone 0721-20596-30; fax 0721-20596-59
----------------------------------------
Motto: Wenn es defekt ist, dann isses kaputt!
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-06 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 10:25 Stephan Linke [this message]
2002-06-06 17:01 ` current->mm Dan Malek
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=FCEAKDJJAPHPLJFINDAJIEFMCFAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).