From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH][GFS2] Lockup on error
Date: Mon, 21 Jan 2008 09:10:58 +0000 [thread overview]
Message-ID: <1200906658.22038.158.camel@quoit> (raw)
In-Reply-To: <1200801024.3640.72.camel@technetium.msp.redhat.com>
Hi,
On Sat, 2008-01-19 at 21:50 -0600, Bob Peterson wrote:
> Hi,
>
> I spotted this bug while I was digging around. Looks like it could cause
> a lockup in some rare error condition.
>
> Regards,
>
> Bob Peterson
> --
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> --
> fs/gfs2/inode.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
Now in the -nmw git tree. Thanks,
Steve.
> diff --git a/fs/gfs2/inode.c b/fs/gfs2/inode.c
> index c84764a..728d316 100644
> --- a/fs/gfs2/inode.c
> +++ b/fs/gfs2/inode.c
> @@ -860,7 +860,7 @@ static int link_dinode(struct gfs2_inode *dip, const struct qstr *name,
>
> error = alloc_required = gfs2_diradd_alloc_required(&dip->i_inode, name);
> if (alloc_required < 0)
> - goto fail;
> + goto fail_quota_locks;
> if (alloc_required) {
> error = gfs2_quota_check(dip, dip->i_inode.i_uid, dip->i_inode.i_gid);
> if (error)
>
>
prev parent reply other threads:[~2008-01-21 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 3:50 [Cluster-devel] [PATCH][GFS2] Lockup on error Bob Peterson
2008-01-21 9:10 ` Steven Whitehouse [this message]
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=1200906658.22038.158.camel@quoit \
--to=swhiteho@redhat.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.