All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v9 2/5] gfs2: iomap buffered write support
Date: Tue, 19 Jun 2018 08:36:24 +0200	[thread overview]
Message-ID: <20180619063624.GC24513@lst.de> (raw)
In-Reply-To: <20180615121922.13237-3-agruenba@redhat.com>

> +/*
> + * Copyright (C) 2017 Red Hat, Inc.  All rights reserved.
> + *
> + * This copyrighted material is made available to anyone wishing to use,
> + * modify, copy, or redistribute it subject to the terms and conditions
> + * of the GNU General Public License version 2.
> + */

Replace with an SPDX tag, please.

> +static int gfs2_iomap_begin_write(struct inode *inode, loff_t pos, loff_t length,

overly long line.

> +		gfs2_write_calc_reserv(ip, iomap->length, &data_blocks, &ind_blocks);

plus a few more down the function.

> +	if (iocb->ki_flags & IOCB_DIRECT)
> +		return generic_file_write_iter(iocb, from);

This looks odd, as generic_file_write_iter duplicate the code
below to a large extent, but it's probably ok.

> @@ -754,7 +786,7 @@ static int fallocate_chunk(struct inode *inode, loff_t offset, loff_t len,
>  		if (error)
>  			goto out;
>  		offset = iomap.offset + iomap.length;
> -		if (iomap.type != IOMAP_HOLE)
> +		if (!(iomap.flags & IOMAP_F_NEW))
>  			continue;

shouldn't this be a separate patch?



WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: cluster-devel@redhat.com, Christoph Hellwig <hch@lst.de>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v9 2/5] gfs2: iomap buffered write support
Date: Tue, 19 Jun 2018 08:36:24 +0200	[thread overview]
Message-ID: <20180619063624.GC24513@lst.de> (raw)
In-Reply-To: <20180615121922.13237-3-agruenba@redhat.com>

> +/*
> + * Copyright (C) 2017 Red Hat, Inc.  All rights reserved.
> + *
> + * This copyrighted material is made available to anyone wishing to use,
> + * modify, copy, or redistribute it subject to the terms and conditions
> + * of the GNU General Public License version 2.
> + */

Replace with an SPDX tag, please.

> +static int gfs2_iomap_begin_write(struct inode *inode, loff_t pos, loff_t length,

overly long line.

> +		gfs2_write_calc_reserv(ip, iomap->length, &data_blocks, &ind_blocks);

plus a few more down the function.

> +	if (iocb->ki_flags & IOCB_DIRECT)
> +		return generic_file_write_iter(iocb, from);

This looks odd, as generic_file_write_iter duplicate the code
below to a large extent, but it's probably ok.

> @@ -754,7 +786,7 @@ static int fallocate_chunk(struct inode *inode, loff_t offset, loff_t len,
>  		if (error)
>  			goto out;
>  		offset = iomap.offset + iomap.length;
> -		if (iomap.type != IOMAP_HOLE)
> +		if (!(iomap.flags & IOMAP_F_NEW))
>  			continue;

shouldn't this be a separate patch?

  reply	other threads:[~2018-06-19  6:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 12:19 [Cluster-devel] [PATCH v9 0/5] gfs2 iomap write support Andreas Gruenbacher
2018-06-15 12:19 ` Andreas Gruenbacher
2018-06-15 12:19 ` [Cluster-devel] [PATCH v9 1/5] iomap: add private pointer to struct iomap Andreas Gruenbacher
2018-06-15 12:19   ` Andreas Gruenbacher
2018-06-18 15:25   ` [Cluster-devel] " Andreas Gruenbacher
2018-06-18 15:25     ` Andreas Gruenbacher
2018-06-19  6:29   ` [Cluster-devel] " Christoph Hellwig
2018-06-19  6:29     ` Christoph Hellwig
2018-06-15 12:19 ` [Cluster-devel] [PATCH v9 2/5] gfs2: iomap buffered write support Andreas Gruenbacher
2018-06-15 12:19   ` Andreas Gruenbacher
2018-06-19  6:36   ` Christoph Hellwig [this message]
2018-06-19  6:36     ` Christoph Hellwig
2018-06-15 12:19 ` [Cluster-devel] [PATCH v9 3/5] gfs2: gfs2_extent_length cleanup Andreas Gruenbacher
2018-06-15 12:19   ` Andreas Gruenbacher
2018-06-15 12:19 ` [Cluster-devel] [PATCH v9 4/5] gfs2: iomap direct I/O support Andreas Gruenbacher
2018-06-15 12:19   ` Andreas Gruenbacher
2018-06-19  6:42   ` [Cluster-devel] " Christoph Hellwig
2018-06-19  6:42     ` Christoph Hellwig
2018-06-20 16:00     ` [Cluster-devel] " Andreas Gruenbacher
2018-06-20 16:00       ` Andreas Gruenbacher
2018-06-15 12:19 ` [Cluster-devel] [PATCH v9 5/5] gfs2: Remove gfs2_write_{begin, end} Andreas Gruenbacher
2018-06-15 12:19   ` [PATCH v9 5/5] gfs2: Remove gfs2_write_{begin,end} Andreas Gruenbacher

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=20180619063624.GC24513@lst.de \
    --to=hch@lst.de \
    /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.