lkml.org 
[lkml]   [2006]   [Apr]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Filesystem & mutex
    On 4/24/06, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
    > Hi,
    >
    > On 4/24/06, Joshua Hudson <joshudson@gmail.com> wrote:
    > > 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.
    >
    > There's no need to 'release' a mutex. If the mutex is unlocked, you
    > can do kmem_cache_free() on the owning inode. You need to do
    > mutex_init() in the object cache constructor (init_once) only because
    > the memory given to you can be arbitrary state. After the mutex has
    > been initialized, it will never go into an illegal state on its own
    > assuming you remember to unlock it before freeing the inode.
    >
    > Pekka
    Tx. Your solution worked.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-04-24 23:28    [W:5.985 / U:0.040 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site