linux-kernel - Re: [V9fs-developer] [PATCH 2/5] fs/9p: Use write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 25 Mar 2011 13:49:32 -0700
From:	Venkateswararao Jujjuri <jvrao@...ux.vnet.ibm.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
CC:	v9fs-developer@...ts.sourceforge.net,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [V9fs-developer] [PATCH 2/5] fs/9p: Use write_inode for data
 sync	on server

On 03/25/2011 04:30 AM, Aneesh Kumar K.V wrote:
> Signed-off-by: Aneesh Kumar K.V<aneesh.kumar@...ux.vnet.ibm.com>

Reviewed-by: Venkateswararao Jujjuri <jvrao@...ux.vnet.ibm.com>
> ---
>   fs/9p/vfs_super.c |   43 +++++++++++++++++++++++++++++++++++++++++++
>   1 files changed, 43 insertions(+), 0 deletions(-)
>
> diff --git a/fs/9p/vfs_super.c b/fs/9p/vfs_super.c
> index f3eed33..d94adcb 100644
> --- a/fs/9p/vfs_super.c
> +++ b/fs/9p/vfs_super.c
> @@ -307,6 +307,47 @@ static int v9fs_drop_inode(struct inode *inode)
>   	return 1;
>   }
>
> +static int v9fs_write_inode(struct inode *inode,
> +			    struct writeback_control *wbc)
> +{
> +	int ret;
> +	struct p9_wstat wstat;
> +	struct v9fs_inode *v9inode;
> +	/*
> +	 * send an fsync request to server irrespective of
> +	 * wbc->sync_mode.
> +	 */
> +	P9_DPRINTK(P9_DEBUG_VFS, "%s: inode %p\n", __func__, inode);
> +	v9inode = V9FS_I(inode);
> +	v9fs_blank_wstat(&wstat);
> +
> +	ret = p9_client_wstat(v9inode->writeback_fid,&wstat);
> +	if (ret<  0) {
> +		__mark_inode_dirty(inode, I_DIRTY_DATASYNC);
> +		return ret;
> +	}
> +	return 0;
> +}
> +
> +static int v9fs_write_inode_dotl(struct inode *inode,
> +				 struct writeback_control *wbc)
> +{
> +	int ret;
> +	struct v9fs_inode *v9inode;
> +	/*
> +	 * send an fsync request to server irrespective of
> +	 * wbc->sync_mode.
> +	 */
> +	P9_DPRINTK(P9_DEBUG_VFS, "%s: inode %p\n", __func__, inode);
> +	v9inode = V9FS_I(inode);
> +	ret = p9_client_fsync(v9inode->writeback_fid, 0);
> +	if (ret<  0) {
> +		__mark_inode_dirty(inode, I_DIRTY_DATASYNC);
> +		return ret;
> +	}
> +	return 0;
> +}
> +
>   static const struct super_operations v9fs_super_ops = {
>   	.alloc_inode = v9fs_alloc_inode,
>   	.destroy_inode = v9fs_destroy_inode,
> @@ -314,6 +355,7 @@ static const struct super_operations v9fs_super_ops = {
>   	.evict_inode = v9fs_evict_inode,
>   	.show_options = generic_show_options,
>   	.umount_begin = v9fs_umount_begin,
> +	.write_inode = v9fs_write_inode,
>   };
>
>   static const struct super_operations v9fs_super_ops_dotl = {
> @@ -325,6 +367,7 @@ static const struct super_operations v9fs_super_ops_dotl = {
>   	.evict_inode = v9fs_evict_inode,
>   	.show_options = generic_show_options,
>   	.umount_begin = v9fs_umount_begin,
> +	.write_inode = v9fs_write_inode_dotl,
>   };
>
>   struct file_system_type v9fs_fs_type = {

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/