From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 22 Aug 2019 16:16:27 -0400 From: Vivek Goyal Message-ID: <20190822201627.GD8999@redhat.com> References: <1566367838-47809-1-git-send-email-bo.liu@linux.alibaba.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1566367838-47809-1-git-send-email-bo.liu@linux.alibaba.com> Subject: Re: [Virtio-fs] [PATCH] virtiofs: fix return value of iomap_begin_upgrade_mapping List-Id: Development discussions about virtio-fs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liu Bo Cc: virtio-fs@redhat.com On Wed, Aug 21, 2019 at 02:10:38PM +0800, Liu Bo wrote: > Set ret = 0 if everything runs fine. > > Signed-off-by: Liu Bo > --- > fs/fuse/file.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/fs/fuse/file.c b/fs/fuse/file.c > index eb7543a..d3c5e45 100644 > --- a/fs/fuse/file.c > +++ b/fs/fuse/file.c > @@ -1985,6 +1985,7 @@ static int iomap_begin_upgrade_mapping(struct inode *inode, loff_t pos, > > out_fill_iomap: > fuse_fill_iomap(inode, pos, length, iomap, dmap, flags); > + ret = 0; Thanks. I initialized ret = 0 in the beginning itself now. Vivek > out_err: > up_write(&fi->i_dmap_sem); > return ret; > -- > 1.8.3.1 > > _______________________________________________ > Virtio-fs mailing list > Virtio-fs@redhat.com > https://www.redhat.com/mailman/listinfo/virtio-fs