All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@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 09:21:45 -0700	[thread overview]
Message-ID: <4DDE7E19.6090307@oracle.com> (raw)
In-Reply-To: <4DDE7CF5.1020101@oracle.com>

On 05/26/2011 09:16 AM, Tristan Ye wrote:
> On 05/27/2011 12:03 AM, Sunil Mushran wrote:
>> Tiger, Thanks. Was this tested with all fs-features enabled? I am
>> worried about quotas. If not, please test that.
>>
>> Tristan, Please can you cross check these patches. Enable all features
>> in a volume, make it readonly and do mount, ls -lR, umount, read, stat,
>> stat -f. This calls for a test script. We should be able to use loopback.
>> losetup -rf.
>
> Sure,
>
> I'm going to write a dedicated script for sanity check, including these
> generic fs syscalls.

Thanks Tristan.

Tiger, I would suggest you roll up the patch into one. I see no reason
for the breakup considering it fixes just one bug and is small enough.

  reply	other threads:[~2011-05-26 16:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  9:40 [Ocfs2-devel] [PATCH 0/4] ocfs2: bugfix for hard readonly mount Tiger Yang
2011-05-26  9:56 ` [Ocfs2-devel] [PATCH 1/4] ocfs2: No need to hangup cluster on " 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 [this message]
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=4DDE7E19.6090307@oracle.com \
    --to=sunil.mushran@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.