Hi Yao, On 22/7/24 06:07, Yao Xingtao via wrote:
Currently, some components still open-coding the range overlap check. Sometimes this check may be fail because some patterns are missed.
How did you catch all these use cases?
To avoid the above problems and improve the readability of the code, it is better to use the ranges_overlap() to do this check. Yao Xingtao (13): range: Make ranges_overlap() return bool arm/boot: make range overlap check more readable core/loader: make range overlap check more readable cxl/mailbox: make range overlap check more readable display/sm501: make range overlap check more readable aspeed_smc: make range overlap check more readable qtest/fuzz: make range overlap check more readable sparc/ldst_helper: make range overlap check more readable system/memory_mapping: make range overlap check more readable block/vhdx: make range overlap check more readable crypto/block-luks: make range overlap check more readable dump: make range overlap check more readable block/qcow2-cluster: make range overlap check more readable
