Re: [PATCH v3 2/2] kernel/resource: fix boundary judgment issues in find_next_iomem_res() and __walk_iomem_res_desc()
From: Dave Hansen
Date: Thu Jul 01 2021 - 12:29:28 EST
On 6/21/21 5:34 AM, Yaohui Wang wrote:
> Memory resources are described with the start address and the inclusive
> end address, which means for a resource with 1 byte length the start
> address is the same as the end address.
Is it just me or does this little "feature" of the resource code
continue to bite us over and over?
It might be some time for some unit tests for kernel/resource.c.