On 27.09.22 11:54, Vlastimil Babka wrote: > On 9/18/22 11:28, Anatoly Pugachev wrote: >> On Fri, Jun 03, 2022 at 07:19:43AM +0300, Vasily Averin wrote: >>> __register_pernet_operations() executes init hook of registered >>> pernet_operation structure in all existing net namespaces. >> [...] >> I'm unable to boot my sparc64 VM anymore (5.19 still boots, 6.0-rc1 does not), >> bisected up to this patch, >> >> mator@ttip:~/linux-2.6$ git bisect bad >> 1d0403d20f6c281cb3d14c5f1db5317caeec48e9 is the first bad commit >> commit 1d0403d20f6c281cb3d14c5f1db5317caeec48e9 >> [...] > > #regzbot introduced: 1d0403d20f6c Thx for getting this regression tracked using regzbot. FWIW, that went sideways (as your already noticed and mentioned on IRC), as that made regzbot treat *your* mail as the report of the regressions. In cases like this you need "#regzbot ^introduced 1d0403d20f6c" (since recently "#regzbot introduced 1d0403d20f6c ^" works, too), as then regzbot will consider the *parent* mail the report (and then regzbot will look out for patches that link to them using a Link: tag). No worries, I did the same mistake a few time already :-D I send a mail with that command now, so let's resolve this subthread by marking it invalid #regzbot invalid: mis-used regzbot command, now properly tracked Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.
