From: jenn <sirpj@ecs.csus.edu>
To: linux-fsdevel@vger.kernel.org
Subject: Re: file system writes
Date: Thu, 13 Jan 2005 16:11:15 -0800 [thread overview]
Message-ID: <1105661475.2977.5.camel@ENERGY> (raw)
In-Reply-To: <20050113213150.GC16884@vagabond>
>
> That being said, it's doable and you are on the right track. Some stupid
> mistake like forgetting to call fput perhaps?
Okay... I changed my calls to use dentry_open and then fput (rather than
filp open and close) and I call dput to release the dentry. The file is
getting written to but I am getting this:
/home/jenn/linux-2.6.6/fs/reiserfs/bitmap.c:915: spin_is_locked on
uninitialized spinlock d48e4e60.
/home/jenn/linux-2.6.6/fs/reiserfs/bitmap.c:917: spin_is_locked on
uninitialized spinlock d48e4e60.
/home/jenn/linux-2.6.6/fs/reiserfs/bitmap.c:883: spin_is_locked on
uninitialized spinlock d48e4e60.
/home/jenn/linux-2.6.6/fs/reiserfs/bitmap.c:885: spin_is_locked on
uninitialized spinlock d48e4e60.
/home/jenn/linux-2.6.6/fs/reiserfs/bitmap.c:902: spin_is_locked on
uninitialized spinlock d48e4e60.
/home/jenn/linux-2.6.6/fs/reiserfs/bitmap.c:904: spin_is_locked on
uninitialized spinlock d48e4e60.
and when I unmount the system I get the dreaded:
Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice
day...
slab error in kmem_cache_destroy(): cache `reiser_inode_cache': Can't
free all objects
>
> But of course, I can't repeat it enough: FILES MUST NOT BE READ NOR
> WRITTEN BY KERNEL!
Well I do have a reason. I wish there were another way.
Jenn
>
> -------------------------------------------------------------------------------
> Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2005-01-14 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 16:53 [PATCH] factor out common code around ->follow_link invocation Christoph Hellwig
2005-01-13 18:35 ` file system writes jenn
2005-01-13 21:31 ` Jan Hudec
2005-01-14 0:11 ` jenn [this message]
2005-01-14 0:06 ` [PATCH] factor out common code around ->follow_link invocation Andrew Morton
2005-01-14 0:21 ` Al Viro
2005-01-14 0:34 ` Andrew Morton
2005-01-14 0:38 ` Al Viro
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=1105661475.2977.5.camel@ENERGY \
--to=sirpj@ecs.csus.edu \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).