From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out30-124.freemail.mail.aliyun.com (out30-124.freemail.mail.aliyun.com [115.124.30.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 171BE36EA96; Thu, 22 Jan 2026 16:37:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=115.124.30.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769099888; cv=none; b=oxX4YFhUVE3yYGuM5YxyXrpd+qraJEMAMu3WWlVpuoZNzlvA1/JorrSgBdlmlHAe0d8CcbGach93SGQXbD94MXUUBPpoCWZilcxB1A4xiaeRgomMSYgUor5t4K+NAkxhfEhvswTyg4QpW+GKkn0EDnRjQTCT6GaOfuiZCkQD90g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769099888; c=relaxed/simple; bh=LXf2sKX1FBNyjxOCtHZ3N3fIjLjX2w8fUDA1/PZlROs=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=A30hsAlUL9g4CcO4BLDMs0MYky5s+wDUajeLezwQ5giyaCQBFa+SnTRJK75hNjlIdnJ/ouAjbKJzV2a9u1X2YoVDWcl5nJNV2l3lq0BQX7oyxBPzj4MoH1dd30Unbf1n20PTgPR1pOksRhffR04ug9OpqJsoTEOmTmzS5WtzIVw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com; spf=pass smtp.mailfrom=linux.alibaba.com; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b=qILSA5H8; arc=none smtp.client-ip=115.124.30.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b="qILSA5H8" DKIM-Signature:v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.alibaba.com; s=default; t=1769099870; h=Message-ID:Date:MIME-Version:Subject:To:From:Content-Type; bh=Lwld6vAnJB2NFeizg3t/vAsO9VfqN5FwLF5cCvhERHo=; b=qILSA5H8zNAYVQ94dKL821X8jG6gwrWSPGW7nmiAdq7LjPVaL6/tqDWeXyeH1J24yVocMHPUThI2SSb6pLIQTKd4xJsSzbsNAEKoT9AVpz0uKvfCsdQoIpfmzcFcO8/yXG8GJbiLPTuIiDw3ELiIvpLj8qbqK3ExXh9x9R57bqI= Received: from 30.180.182.138(mailfrom:hsiangkao@linux.alibaba.com fp:SMTPD_---0Wxcwr5W_1769099868 cluster:ay36) by smtp.aliyun-inc.com; Fri, 23 Jan 2026 00:37:49 +0800 Message-ID: Date: Fri, 23 Jan 2026 00:37:48 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v17 07/10] erofs: pass inode to trace_erofs_read_folio To: Hongbo Li Cc: hch@lst.de, djwong@kernel.org, amir73il@gmail.com, linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org, brauner@kernel.org, chao@kernel.org References: <20260122153406.660073-1-lihongbo22@huawei.com> <20260122153406.660073-8-lihongbo22@huawei.com> From: Gao Xiang In-Reply-To: <20260122153406.660073-8-lihongbo22@huawei.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2026/1/22 23:34, Hongbo Li wrote: > The trace_erofs_read_folio accesses inode information through folio, > but this method fails if the real inode is not associated with the > folio(such as for the uncomping page cache sharing case). Therefore, ^ in the upcoming > we pass the real inode to it so that the inode information can be > printed out in that case. > > Signed-off-by: Hongbo Li Reviewed-by: Gao Xiang Thanks, Gao Xiang