linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Hou Tao <houtao1@huawei.com>
Cc: v9fs-developer@lists.sourceforge.net, lucho@ionkov.net,
	ericvh@gmail.com, linux-fsdevel@vger.kernel.org,
	xingaopeng@huawei.com
Subject: Re: [PATCH v3 1/2] 9p: use inode->i_lock to protect i_size_write() under 32-bit
Date: Thu, 24 Jan 2019 07:57:33 +0100	[thread overview]
Message-ID: <20190124065733.GA21444@nautica> (raw)
In-Reply-To: <20190124063514.8571-2-houtao1@huawei.com>

Hou Tao wrote on Thu, Jan 24, 2019:
> @@ -83,4 +88,17 @@ static inline void v9fs_invalidate_inode_attr(struct inode *inode)
>  }
>  
>  int v9fs_open_to_dotl_flags(int flags);
> +
> +static inline void v9fs_i_size_write(struct inode *inode, loff_t i_size)
> +{
> +	/*
> +	 * Avoid taking i_lock under 64-bit.
> +	 * Refer to fsstack_copy_inode_size() for detailed explanation.
> +	 */

Just one last nitpick here: I'd rather not reference to another function
for comment; the 9p code doesn't change much and if someone ever changes
fsstack_copy_inode_size it'll probably go unnoticed for a while.

If you're OK with this I can change it myself, but got other comments
for second patch so up to you.

More than happy with the rest, I'll run some tests over the weekend for
the sake of it but should take this patch to -next early next week
assuming we agree on something for the comment.

-- 
Dominique

  reply	other threads:[~2019-01-24  6:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  6:35 [PATCH v3 0/2] use i_lock to protect updates of i_blocks & Hou Tao
2019-01-24  6:35 ` [PATCH v3 1/2] 9p: use inode->i_lock to protect i_size_write() under 32-bit Hou Tao
2019-01-24  6:57   ` Dominique Martinet [this message]
2019-01-24 11:01     ` Hou Tao
2019-03-02 11:31     ` Hou Tao
2019-03-03  4:57       ` Dominique Martinet
2019-01-24  6:35 ` [PATCH v3 2/2] 9p: use i_lock to protect update of inode->i_blocks " Hou Tao
2019-01-24  7:25   ` Dominique Martinet
2019-01-24 14:03     ` Hou Tao
2019-01-24 14:45       ` Dominique Martinet
2019-01-24 14:53         ` Dominique Martinet

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=20190124065733.GA21444@nautica \
    --to=asmadeus@codewreck.org \
    --cc=ericvh@gmail.com \
    --cc=houtao1@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=xingaopeng@huawei.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).