From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Steve French" <smfrench@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Can kmem_cache_free block?
Date: Sat, 29 Mar 2008 12:15:36 +1100 [thread overview]
Message-ID: <200803291215.37108.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <524f69650803281223v5e54e1c1na8a46da2e0a3df4c@mail.gmail.com>
On Saturday 29 March 2008 06:23, Steve French wrote:
> Is kmem_cache_free safe to call while holding a spinlock (can
> kmem_cache_free ever block or recurse into a file system)?
>
> I see it trying to grab just another spinlock which is probably fine
> (but was worried whether any of the worker functions called a sem) ...
> my assumption is that it would be safe, but the man page doesn't
> mention when it can be used safely.
Yes you can call it from any context.
prev parent reply other threads:[~2008-03-29 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 19:23 Steve French
2008-03-29 1:15 ` Nick Piggin [this message]
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=200803291215.37108.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.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
all inboxes | Powered by JetHome®