cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Fix allocation error bug with recursive rgrp glocking
Date: Thu, 31 May 2018 08:26:46 -0400 (EDT)	[thread overview]
Message-ID: <711845674.38892813.1527769606813.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180531110823.29096-1-agruenba@redhat.com>

----- Original Message -----
> Bob,
> 
> On 30 May 2018 at 21:14, Bob Peterson <rpeterso@redhat.com> wrote:
> > Before this patch function gfs2_write_begin, upon discovering an
> > error, called gfs2_trim_blocks while the rgrp glock was still held.
> > That's because gfs2_inplace_release is not called until later.
> 
> agreed.
> 
> > This patch reorganizes the logic a bit so gfs2_inplace_release
> > is called to release the lock prior to the call to gfs2_trim_blocks,
> > thus preventing the glock recursion.
> 
> gfs2_trim_blocks only needs to be called after __block_write_begin but
> with your proposed patch, it also ends up being called on other error
> paths.  This complicates gfs2_write_begin, so how about the below patch
> instead?
> 
> Thanks,
> Andreas

Hi Andreas,

My previous version looked a lot like yours, so yes, I'll take your
version instead. It's going to be overwritten by your iomap-write
patch set eventually anyway.

Regards,

Bob Peterson



      reply	other threads:[~2018-05-31 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <97915428.38585535.1527707643430.JavaMail.zimbra@redhat.com>
2018-05-30 19:14 ` [Cluster-devel] [GFS2 PATCH] GFS2: Fix allocation error bug with recursive rgrp glocking Bob Peterson
2018-05-31 11:08   ` Andreas Gruenbacher
2018-05-31 12:26     ` Bob Peterson [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=711845674.38892813.1527769606813.JavaMail.zimbra@redhat.com \
    --to=rpeterso@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).