[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAM9Jb+hUk_e-Un3+9Jx8eKDtZ2A597bawQTJXQx77T0yG+PdnQ@mail.gmail.com>
Date: Thu, 30 Jul 2020 06:33:14 +0200
From: Pankaj Gupta <pankaj.gupta.linux@...il.com>
To: Hao Li <lihao2018.fnst@...fujitsu.com>
Cc: viro@...iv.linux.org.uk, Matthew Wilcox <willy@...radead.org>,
Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org,
linux-nvdimm@...ts.01.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dax: Fix wrong error-number passed into xas_set_err()
> The error-number passed into xas_set_err() should be negative. Otherwise,
> the xas_error() will return 0, and grab_mapping_entry() will return the
> found entry instead of a SIGBUS error when the entry is not a value.
> And then, the subsequent code path would be wrong.
>
> Signed-off-by: Hao Li <lihao2018.fnst@...fujitsu.com>
> ---
> fs/dax.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/dax.c b/fs/dax.c
> index 11b16729b86f..acac675fe7a6 100644
> --- a/fs/dax.c
> +++ b/fs/dax.c
> @@ -488,7 +488,7 @@ static void *grab_mapping_entry(struct xa_state *xas,
> if (dax_is_conflict(entry))
> goto fallback;
> if (!xa_is_value(entry)) {
> - xas_set_err(xas, EIO);
> + xas_set_err(xas, -EIO);
> goto out_unlock;
> }
>
> --
Reviewed-by: Pankaj Gupta <pankaj.gupta.linux@...il.com>
> 2.28.0
>
>
> _______________________________________________
> Linux-nvdimm mailing list -- linux-nvdimm@...ts.01.org
> To unsubscribe send an email to linux-nvdimm-leave@...ts.01.org
Powered by blists - more mailing lists