On 12/28/19 7:32 PM, Ming Lei wrote: > There are two issues in get_max_segment_size(): > > 1) the default segment boudary mask is bypassed, and some devices still > require segment to not cross the default 4G boundary > > 2) the segment start address isn't taken into account when checking > segment boundary limit > > Fixes the two issues. Given the potential severity of the bug, I think it deserves a somewhat richer explanation than just that. It should also go into stable. This is what I queued up: https://git.kernel.dk/cgit/linux-block/commit/?h=block-5.5&id=add1fc07334260253dfa880d9c964edc8381deac BTW, did you change your email setup recently? Your patches are coming through mangled. -- Jens Axboe