From: "dan carpenter" <error27@email.com>
To: linux-kernel@vger.kernel.org
Cc: mnalis-umsdos@voyager.hr, smatch-kbugs@lists.sf.net
Subject: declaring large variables
Date: Sat, 16 Nov 2002 18:57:25 -0500 [thread overview]
Message-ID: <20021116235725.10323.qmail@email.com> (raw)
I have a program (smatch.sf.net) that checks for certain types of kernel coding errors. I'm working on one that checks for functions that possibly put too much data on the 8kB local variable stack. The function UMSDOS_ioctl_dir puts less than 2kB of data so it's probably not a problem. Especially since it doesn't do that for all code paths.
What should be the upper limit for how much data a function can put on the stack.
linux-2.5.44/fs/umsdos/ioctl.c 439 UMSDOS_ioctl_dir (14432 bits)
Line Variable Size
79 struct umsdos_ioctl data; (4736 bits)
177 struct umsdos_dirent entry; (2048 bits)
178 struct umsdos_info info; (2304 bits)
250 struct umsdos_info info; (2304 bits)
305 struct umsdos_info info; (2304 bits)
Regards,
dan carpenter
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Single & ready to mingle? lavalife.com: Where singles click. Free to Search!
http://www.lavalife.com/wp.epl?a=2716
reply other threads:[~2002-11-16 23:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021116235725.10323.qmail@email.com \
--to=error27@email.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnalis-umsdos@voyager.hr \
--cc=smatch-kbugs@lists.sf.net \
/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