From: arjan@fenrus.demon.nl
To: engler@csl.Stanford.EDU (Dawson Engler)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] error path memory leaks in 2.4.4 and 2.4.4-ac8
Date: Fri, 25 May 2001 08:21:04 +0100 (BST) [thread overview]
Message-ID: <m153BuC-000OiPC@amadeus.home.nl> (raw)
In-Reply-To: <200105250238.TAA00788@csl.Stanford.EDU>
In article <200105250238.TAA00788@csl.Stanford.EDU> you wrote:
>> I believe we can make that a short. Arjan?
> Is the general way to fix these too-large stack vars to heap allocate
> them? Or is it preferable to put a "static" in front of them, if the
> routine is non-reentrant?
You're not always allowed to allocate memory. Esp in filesystems it can be
tricky as writes can be triggered by low-memory situations and allocating
memory their is suboptimal.
next prev parent reply other threads:[~2001-05-25 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 21:07 Dawson Engler
2001-05-24 22:02 ` David Woodhouse
2001-05-25 2:38 ` Dawson Engler
2001-05-25 7:21 ` arjan [this message]
2001-05-24 23:07 ` Alan Cox
2001-05-25 2:54 ` Dawson Engler
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=m153BuC-000OiPC@amadeus.home.nl \
--to=arjan@fenrus.demon.nl \
--cc=engler@csl.Stanford.EDU \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®