From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] OCFS2: anti stale inode for nfs (V5)
Date: Fri, 27 Feb 2009 18:22:36 -0800 [thread overview]
Message-ID: <20090228022236.GK10695@mail.oracle.com> (raw)
In-Reply-To: <200902271234.n1RCYbZ2022526@rgminet15.oracle.com>
On Fri, Feb 27, 2009 at 08:33:28PM +0800, wengang wang wrote:
> changes from v4:
> 1, let suballoc lock covers the checking of the group.
>
> 2, add/correct some log messages.
>
> 3, use ocfs2_read_group_descriptor() instead of diry reading the group.
>
> Signed-off-by: Wengang Wang <wen.gang.wang@oracle.com>
Almost there!
> + bg_blkno = ocfs2_which_suballoc_group(blkno, bit);
> + status = ocfs2_read_group_descriptor(suballoc, alloc_fe, bg_blkno,
> + &group_bh);
> + if (status < 0) {
> + mlog(ML_ERROR, "read group %llu failed %d\n", bg_blkno, status);
> + goto bail;
> + }
> +
> + status = ocfs2_check_group_descriptor(osb->sb, alloc_fe, group_bh);
> + if (status < 0) {
> + mlog(ML_ERROR, "check group %llu faild %d\n", bg_blkno, status);
> + goto bail;
> + }
The call to ocfs2_read_group_descriptor() already does the same
checkin as ocfs2_check_group_descriptor(), so you don't need to call
ocfs2_check_group_descriptor().
Other than that, I think this patch is done! Do you have a test
to test it?
Joel
--
One look at the From:
understanding has blossomed
.procmailrc grows
- Alexander Viro
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-02-28 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 12:33 [Ocfs2-devel] [PATCH 1/1] OCFS2: anti stale inode for nfs (V5) wengang wang
2009-02-28 2:22 ` Joel Becker [this message]
2009-03-02 2:16 ` Wengang Wang
2009-03-02 8:08 ` Joel Becker
2009-03-02 8:28 ` Wengang Wang
2009-03-02 21:57 ` Joel Becker
2009-03-03 2:28 ` Wengang Wang
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=20090228022236.GK10695@mail.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.