From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <ramands@indiatimes.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-newbie@vger.kernel.org>
Subject: Re: OOPS in Kmalloc
Date: Wed, 23 Apr 2003 21:34:58 -0700 (PDT) [thread overview]
Message-ID: <32992.4.64.197.106.1051158898.squirrel@www.osdl.org> (raw)
In-Reply-To: <200304240344.JAA29170@WS0005.indiatimes.com>
> Hello,
> i am getting OOPS in Kmalloc .
>
> void **data;
> qset = 1000;
>
> dptr->data = kmalloc(qset * sizeof(char *), GFP_KERNEL);
>
> what could the possible the cause of the error
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As I am so fond of saying, it's almost always correct to indicate what
kernel version one if referring to in a problem report.
Please decode the oops output and post it here.
~Randy
next prev parent reply other threads:[~2003-04-24 4:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 4:16 OOPS in Kmalloc ramands
2003-04-24 4:34 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 8:45 ramands
2003-04-24 17:20 ` Randy.Dunlap
2003-04-23 3:41 oops in kmalloc ramands
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=32992.4.64.197.106.1051158898.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=ramands@indiatimes.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 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).