[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190818123314.GA29733@bombadil.infradead.org>
Date: Sun, 18 Aug 2019 05:33:14 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Gao Xiang <hsiangkao@....com>
Cc: Chao Yu <yuchao0@...wei.com>, Richard Weinberger <richard@....at>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org, linux-fsdevel@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
linux-erofs@...ts.ozlabs.org, Chao Yu <chao@...nel.org>,
Miao Xie <miaoxie@...wei.com>, Fang Wei <fangwei1@...wei.com>,
Gao Xiang <gaoxiang25@...wei.com>, stable@...r.kernel.org
Subject: Re: [PATCH v3 RESEND] staging: erofs: fix an error handling in
erofs_readdir()
On Sun, Aug 18, 2019 at 11:21:11AM +0800, Gao Xiang wrote:
> + if (dentry_page == ERR_PTR(-ENOMEM)) {
> + errln("no memory to readdir of logical block %u of nid %llu",
> + i, EROFS_V(dir)->nid);
I don't think you need the error message. If we get a memory allocation
failure, there's already going to be a lot of spew in the logs from the
mm system. And if we do fail to allocate memory, we don't need to know
the logical block number or the nid -- it has nothiing to do with those;
the system simply ran out of memory.
> + err = -ENOMEM;
> + break;
> + } else if (IS_ERR(dentry_page)) {
> + errln("fail to readdir of logical block %u of nid %llu",
> + i, EROFS_V(dir)->nid);
> + err = -EFSCORRUPTED;
> + break;
> + }
>
> de = (struct erofs_dirent *)kmap(dentry_page);
>
> --
> 2.17.1
>
Powered by blists - more mailing lists