From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] What's your opinion on the patch to fix bug 58 for kernel 2.6 porting?
Date: Fri Apr 30 11:57:27 2004 [thread overview]
Message-ID: <20040430165258.GD26744@ca-server1.us.oracle.com> (raw)
In-Reply-To: <37FBBA5F3A361C41AB7CE44558C3448E03B65E95@PDSMSX403.ccr.corp.intel.com>
On Fri, Apr 30, 2004 at 09:19:19AM +0800, Zhang, Sonic wrote:
> In kernel 2.6 VFS routine sys_umount()->...->generic_shutdown_super(), if the inode usage count i_count is not 0, error information is reported. Then, the system will halt in routine kill_bdev()->truncate_inode_pages().
> If we don't fix it in OCFS2 driver, we have to change the kernel 2.6 VFS sys_umount code. Is it a good solution?
The issue is not whether to fix it in the OCFS2 driver. The
issue is solving the problem without resorting to ugly stuff like
signals.
Can you provide a complete description of what happens to cause
the problem, so we can look at it?
Joel
--
"Depend on the rabbit's foot if you will, but remember, it didn't
help the rabbit."
- R. E. Shay
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2004-04-30 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 20:20 [Ocfs2-devel] What's your opinion on the patch to fix bug 58 for kernel 2.6 porting? Zhang, Sonic
2004-04-30 11:57 ` Joel Becker [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-04 1:08 Zhang, Sonic
2004-04-28 21:11 Zhang, Sonic
2004-04-29 12:34 ` Mark Fasheh
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=20040430165258.GD26744@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.