From: ebiederm@xmission.com (Eric W. Biederman)
To: Timur Tabi <ttabi@interactivesi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kernel hangs in 118th call to vmalloc
Date: 08 Sep 2001 12:30:41 -0600 [thread overview]
Message-ID: <m1ae05h6we.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3B8FDA36.5010206@interactivesi.com>
In-Reply-To: <3B8FDA36.5010206@interactivesi.com>
Timur Tabi <ttabi@interactivesi.com> writes:
> I'm writing a driver for the 2.4.2 kernel. I need to use this kernel because
> this driver needs to be compatible with a stock Red Hat system. Patches to the
> kernel are not an option.
>
> The purpose of the driver is to locate a device that exists on a specific memory
>
> chip. To help find it, I've written this routine:
What is wrong with using SPD to detect interesting properties of
memory chips? That should be safer and usually easier then what you
are trying now.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Timur Tabi <ttabi@interactivesi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kernel hangs in 118th call to vmalloc
Date: 08 Sep 2001 12:30:41 -0600 [thread overview]
Message-ID: <m1ae05h6we.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3B8FDA36.5010206@interactivesi.com>
Timur Tabi <ttabi@interactivesi.com> writes:
> I'm writing a driver for the 2.4.2 kernel. I need to use this kernel because
> this driver needs to be compatible with a stock Red Hat system. Patches to the
> kernel are not an option.
>
> The purpose of the driver is to locate a device that exists on a specific memory
>
> chip. To help find it, I've written this routine:
What is wrong with using SPD to detect interesting properties of
memory chips? That should be safer and usually easier then what you
are trying now.
Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-09-08 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 18:40 kernel hangs in 118th call to vmalloc Timur Tabi
2001-08-31 18:40 ` Timur Tabi
2001-08-31 20:38 ` Alan Cox
2001-08-31 20:38 ` Alan Cox
2001-08-31 20:41 ` Timur Tabi
2001-08-31 20:54 ` Alan Cox
2001-09-08 18:30 ` Eric W. Biederman [this message]
2001-09-08 18:30 ` Eric W. Biederman
2001-09-08 19:39 ` Timur Tabi
2001-09-08 19:39 ` Timur Tabi
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=m1ae05h6we.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ttabi@interactivesi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.