From: "Joshua Hudson" <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Filesystem & mutex
Date: Sun, 23 Apr 2006 21:54:13 -0700 [thread overview]
Message-ID: <bda6d13a0604232154r28f23212o55b15a065fe6d648@mail.gmail.com> (raw)
My filesystem has need of an extra mutex in the extended inode data area.
>From what I understand, the mutex can be initalized in inode_init_once, but
I cannot determine how to free it.
It looks wrong to destroy the mutex by just destroying the slab.
It is wrong to destroy the inode in destroy_inode. Badness when
an inode is reused.
I really don't want to go back to semaphores. The mutex code just *looks* so
much cleaner.
next reply other threads:[~2006-04-24 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 4:54 Joshua Hudson [this message]
2006-04-24 11:19 ` Pekka Enberg
2006-04-24 21:24 ` Joshua Hudson
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=bda6d13a0604232154r28f23212o55b15a065fe6d648@mail.gmail.com \
--to=joshudson@gmail.com \
--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®