From: Manfred Spraul <manfred@colorfullife.com>
To: Kernel Stuff <kernel-stuff@comcast.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] Document kfree and vfree NULL usage (resend)
Date: Sun, 05 Dec 2004 18:57:57 +0100 [thread overview]
Message-ID: <41B34C25.3060500@colorfullife.com> (raw)
In-Reply-To: <200412051244.36449.kernel-stuff@comcast.net>
Kernel Stuff wrote:
>The attached patch changes the vfree() documentation to correct "May not be
>called in interrupt context" to "Must not be called in interrupt context".
>Latter is compliant to RFC2119 and matches the absolute requirement for
>vfree.
>
>Is not the same requirement true for vmalloc() - or is it ok to call vmalloc()
>in interrupt?
>
>
>
No, it's not ok.
But that's not something worth mentioning: only a few functions are
permitted from interrupt context. The special thing about vfree is the
asymmetry: kfree from irq context is ok, vfree is forbidden. That's why
it's documented.
--
Manfred
next prev parent reply other threads:[~2004-12-05 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 19:48 [PATCH] Document kfree and vfree NULL usage (resend) Pekka Enberg
2004-12-05 15:33 ` Manfred Spraul
2004-12-05 16:05 ` Kernel Stuff
2004-12-05 16:59 ` Manfred Spraul
2004-12-05 17:44 ` Kernel Stuff
2004-12-05 17:57 ` Manfred Spraul [this message]
2004-12-05 18:12 ` Parag Warudkar
2004-12-05 20:29 ` Pekka Enberg
[not found] ` <200412051648.08283.kernel-stuff@comcast.net>
2004-12-06 8:09 ` Pekka Enberg
2004-12-05 20:21 ` Pekka Enberg
2004-12-05 20:38 ` Parag Warudkar
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=41B34C25.3060500@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@osdl.org \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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