From: "ramands" <ramands@indiatimes.com>
To: <linux-kernel@vger.kernel.org>, <linux-newbie@vger.kernel.org>
Cc: <whitnl73@juno.com>, <ray@comarre.com>, <sneakums@zork.net>
Subject: OOPS in Kmalloc
Date: Thu, 24 Apr 2003 09:46:17 +0530 [thread overview]
Message-ID: <200304240344.JAA29170@WS0005.indiatimes.com> (raw)
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
Raman
Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com
Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com
Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now !
next reply other threads:[~2003-04-24 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 4:16 ramands [this message]
2003-04-24 4:34 ` OOPS in Kmalloc Randy.Dunlap
-- 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=200304240344.JAA29170@WS0005.indiatimes.com \
--to=ramands@indiatimes.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
--cc=sneakums@zork.net \
--cc=whitnl73@juno.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).