From: Tiger Yang <tiger.yang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/4] ocfs2: bugfix for hard readonly mount
Date: Thu, 26 May 2011 17:40:16 +0800 [thread overview]
Message-ID: <4DDE2000.3000301@oracle.com> (raw)
Hi, All,
These four patches are all related to ocfs2 on hard readonly mount.
patch 1 fix oops when umount ocfs2 on hard readonly device.
Because ocfs2_dismount_volume() will call ocfs2_cluster_hangup() and
then call ocfs2_stack_driver_put(), will hit BUG_ON(active_stack == NULL).
patch 2 fix oops when do ls or cat in ocfs2 on hard readonly device.
Because ocfs2_open_lock() will call ocfs2_cluster_lock() and then call
ocfs2_dlm_lock(), but active_stack is NULL.
patch 3 fix bug of http://oss.oracle.com/bugzilla/show_bug.cgi?id=1322
ocfs2_statfs, ocfs2_fiemap, ocfs2_get_acl, ocfs2_listxattr and
ocfs2_xattr_get need ocfs2_inode_lock to get dinode buffer head, but on
hard readonly mount, they did not get they expected, so lead to oops.
ocfs2_init_security_and_acl and ocfs2_test_inode_bit also called
ocfs2_inode_lock(inode, &bh, 0), but they are safe, because
ocfs2_reflink and ocfs2_get_dentry check hard read only before them.
patch 4 fix problem of running ls on hard readonly mount can't get the
right result.
Because ocfs2_dentry_lock() return -EROFS. It should return 0.
best regards,
Tiger
next reply other threads:[~2011-05-26 9:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 9:40 Tiger Yang [this message]
2011-05-26 9:56 ` [Ocfs2-devel] [PATCH 1/4] ocfs2: No need to hangup cluster on hard readonly mount Tiger Yang
2011-05-26 9:57 ` [Ocfs2-devel] [PATCH 2/4] ocfs2: Add hard readonly check in open lock Tiger Yang
2011-05-26 9:57 ` [Ocfs2-devel] [PATCH 3/4] ocfs2: Get dinode buffer head on hard readonly mount Tiger Yang
2011-05-26 9:58 ` [Ocfs2-devel] [PATCH 4/4] ocfs2: Get readonly dentry lock " Tiger Yang
2011-05-26 16:03 ` [Ocfs2-devel] [PATCH 0/4] ocfs2: bugfix for " Sunil Mushran
2011-05-26 16:16 ` Tristan Ye
2011-05-26 16:21 ` Sunil Mushran
2011-06-02 3:09 ` Tristan Ye
2011-06-02 18:43 ` Sunil Mushran
2011-06-03 1:00 ` Tristan Ye
2011-06-03 1:05 ` Sunil Mushran
2011-06-03 1:14 ` Tristan Ye
2011-05-26 16:21 ` Tristan Ye
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=4DDE2000.3000301@oracle.com \
--to=tiger.yang@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.