On 18/06/2021 17:00, Matthew Wilcox wrote:
On Fri, Jun 18, 2021 at 04:55:23PM +0200, Krzysztof Kozlowski wrote:
> These are randconfigs, so I don't think Linus will hit them when
> merging. Therefore assuming the reset-stubs are applied (and tree is in
> next), we should be fine, shouldn't we?
It's a bisection hazard. Please fix it before the merge. This is
exactly the kind of thing that linux-next is designed to detect.
Still hazard for a compile testing configuration, not a real bisection
for troubleshooting bugs. You cannot hit the bug in any real case (so
!COMPILE_TEST).
The only way to reduce the bisection hazard is me to take reset stubs.
Best regards,
Krzysztof