cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH v2] GFS2: dirty inode correctly in gfs2_iomap_end for jdata
Date: Tue, 3 Jul 2018 20:32:28 +0200	[thread overview]
Message-ID: <CAHc6FU59vpTyTkz2RMiLQymNXOZ2-LU3Cc56jf4ZEVUS7Cs91A@mail.gmail.com> (raw)
In-Reply-To: <585695489.47735798.1530629665843.JavaMail.zimbra@redhat.com>

On 3 July 2018 at 16:54, Bob Peterson <rpeterso@redhat.com> wrote:
> Hi,
>
> I posted an equivalent patch on 18 June which was largely ignored.
> This is revised for the recent iomap changes.
> ---
> In patch 0c9018097f, function gfs2_write_end was changed so that it
> marked inodes dirty if they had new buffers queued to the current
> transaction. Unfortunately, it was only done for ordered data files.
> The check was never done for jdata files, so the inode was never
> properly marked dirty. The affected code has since been moved to
> function gfs2_iomap_end. This patch adds the additional check so
> that jdata files are also marked dirty.

Like I just said in the previous posting of this fix, I'd be much
happier to have a test case.

> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
>  fs/gfs2/bmap.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c
> index 49a6ab919bd7..afbee7e4ae5b 100644
> --- a/fs/gfs2/bmap.c
> +++ b/fs/gfs2/bmap.c
> @@ -1116,7 +1116,7 @@ static int gfs2_iomap_end(struct inode *inode, loff_t pos, loff_t length,
>         if (iomap->type != IOMAP_INLINE) {
>                 gfs2_ordered_add_inode(ip);
>
> -               if (tr->tr_num_buf_new)
> +               if (tr->tr_num_buf_new || tr->tr_num_databuf_new)
>                         __mark_inode_dirty(inode, I_DIRTY_DATASYNC);
>                 else
>                         gfs2_trans_add_meta(ip->i_gl, dibh);
>

Thanks,
Andreas



      reply	other threads:[~2018-07-03 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1441162328.47734988.1530629474646.JavaMail.zimbra@redhat.com>
2018-07-03 14:54 ` [Cluster-devel] [GFS2 PATCH v2] GFS2: dirty inode correctly in gfs2_iomap_end for jdata Bob Peterson
2018-07-03 18:32   ` Andreas Gruenbacher [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=CAHc6FU59vpTyTkz2RMiLQymNXOZ2-LU3Cc56jf4ZEVUS7Cs91A@mail.gmail.com \
    --to=agruenba@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).