From: "dan carpenter" <error27@email.com>
To: nfs@lists.sourceforge.net
Cc: smatch-kbugs@lists.sourceforge.net
Subject: declaring large variables
Date: Sat, 16 Nov 2002 18:04:20 -0500 [thread overview]
Message-ID: <20021116230420.29059.qmail@email.com> (raw)
I have a project smatch.sf.net that checks the kernel for certain types of errors. My newest code checks that functions do not declare too much data to fit on the kernel's 8kB stack. These functions both use up 2.5kB (16512b) so they're probably not a problem. But it might be worth declaring nfsctl_export as a pointer and using kmalloc to set aside memory.
linux-2.5.44/fs/nfsd/nfsctl.c 212 write_export 16512
linux-2.5.44/fs/nfsd/nfsctl.c 222 write_unexport 16512
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
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-11-16 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 23:04 dan carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-16 23:57 declaring large variables dan carpenter
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=20021116230420.29059.qmail@email.com \
--to=error27@email.com \
--cc=nfs@lists.sourceforge.net \
--cc=smatch-kbugs@lists.sourceforge.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 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.