[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c424dfd-8ca0-6614-903f-a37dac818d27@huawei.com>
Date: Sat, 30 Mar 2024 09:19:37 +0800
From: "zhangpeng (AS)" <zhangpeng362@...wei.com>
To: Dexuan Cui <decui@...rosoft.com>, <hch@....de>,
<m.szyprowski@...sung.com>, <robin.murphy@....com>, <iommu@...ts.linux.dev>,
<mhklinux@...look.com>
CC: <linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>
Subject: Re: [PATCH] swiotlb: Do not set total_used to 0 in
swiotlb_create_debugfs_files()
On 2024/3/30 3:28, Dexuan Cui wrote:
> Sometimes the readout of /sys/kernel/debug/swiotlb/io_tlb_used and
> io_tlb_used_hiwater can be a huge number (e.g. 18446744073709551615),
> which is actually a negative number if we use "%ld" to print the number.
>
> When swiotlb_create_default_debugfs() is running from late_initcall,
> mem->total_used may already be non-zero, because the storage driver
> may have already started to perform I/O operations: if the storage
> driver is built-in, its probe() callback is called before late_initcall.
>
> swiotlb_create_debugfs_files() should not blindly set mem->total_used
> and mem->used_hiwater to 0; actually it doesn't have to initialize the
> fields at all, because the fields, as part of the global struct
> io_tlb_default_mem, have been implicitly initialized to zero.
>
> Also don't explicitly set mem->transient_nslabs to 0.
>
> Fixes: 8b0977ecc8b3 ("swiotlb: track and report io_tlb_used high water marks in debugfs")
> Fixes: 02e765697038 ("swiotlb: add debugfs to track swiotlb transient pool usage")
> Cc: stable@...r.kernel.org
> Signed-off-by: Dexuan Cui <decui@...rosoft.com>
Reviewed-by: ZhangPeng<zhangpeng362@...wei.com>
--
Best Regards,
Peng
Powered by blists - more mailing lists