| Message ID | 20181017062138.1721-1-christophe.jaillet@wanadoo.fr (mailing list archive) |
|---|---|
| State | Accepted |
| Headers | show |
| Series | xfs: Fix error code in 'xfs_ioc_getbmap()' | expand |
On Wed, Oct 17, 2018 at 08:21:38AM +0200, Christophe JAILLET wrote: > In this function, once 'buf' has been allocated, we unconditionally > return 0. > However, 'error' is set to some error codes in several error handling > paths. > Before commit 232b51948b99 ("xfs: simplify the xfs_getbmap interface") > this was not an issue because all error paths were returning directly, > but now that some cleanup at the end may be needed, we must propagate the > error code. > > Fixes: 232b51948b99 ("xfs: simplify the xfs_getbmap interface") > Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr> Looks good: Reviewed-by: Christoph Hellwig <hch@lst.de>
diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c index 0ef5ece5634c..bad90479ade2 100644 --- a/fs/xfs/xfs_ioctl.c +++ b/fs/xfs/xfs_ioctl.c @@ -1616,7 +1616,7 @@ xfs_ioc_getbmap( error = 0; out_free_buf: kmem_free(buf); - return 0; + return error; } struct getfsmap_info {
In this function, once 'buf' has been allocated, we unconditionally return 0. However, 'error' is set to some error codes in several error handling paths. Before commit 232b51948b99 ("xfs: simplify the xfs_getbmap interface") this was not an issue because all error paths were returning directly, but now that some cleanup at the end may be needed, we must propagate the error code. Fixes: 232b51948b99 ("xfs: simplify the xfs_getbmap interface") Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr> --- fs/xfs/xfs_ioctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)