Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 26 Nov 2020 10:50:04 +0100
From:   Christoph Hellwig <hch@lst.de>
To:     Yicong Yang <yangyicong@hisilicon.com>
Cc:     Christoph Hellwig <hch@lst.de>, viro@zeniv.linux.org.uk,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        prime.zeng@huawei.com, linuxarm@huawei.com
Subject: Re: [PATCH] fs: export vfs_stat() and vfs_fstatat()
Message-ID: <20201126095004.GA23930@lst.de>
References: <1606374948-38713-1-git-send-email-yangyicong@hisilicon.com> <20201126071848.GA17990@lst.de> <696f0e06-4f4d-0a61-6e13-f5af433594bf@hisilicon.com> <20201126091537.GA21957@lst.de> <79b19660-f418-f5ac-943c-bc49a88eb949@hisilicon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <79b19660-f418-f5ac-943c-bc49a88eb949@hisilicon.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Precedence: bulk

On Thu, Nov 26, 2020 at 05:48:25PM +0800, Yicong Yang wrote:
> Sorry for not describing the issues I met correctly in the commit message.
> Actually we're using inline function vfs_stat() for getting the
> attributes, which calls vfs_fstatat():

Again, there generally isn't much need to look at the stat data
for an in-kernel caller.  But without you submitting the code I can't
really help you anyway.