On Thu, Apr 9, 2020 at 5:55 AM Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote:
>
> linux-next is boot-broken for more than a month and bugs are piling
> onto bugs, I've seen at least 3 different ones.
> syzbot can't get any working linux-next build for testing for a very
> long time now.
Ouch.
Ok, that's not good. It means that linux-next has basically only done
build-testing this whole cycle.
Stephen, Dmitry - is there some way linux-next could possibly kick out
trees more aggressively if syzbot can't even boot?
This merge window has seemed otherwise fairly smooth to me (famous
last words), and it's really sad how the nice page fault cleanups
ended up being such an ongoing pain when the problems _could_ have
been caught earlier. We started to get syzbot reports very quickly
after they got merged into my tree, so this is clearly something that
gets exercised well - but it would have been oh-so-much better if it
had gotten noticed in linux-next.
Kicking trees out of linux-next and making noise if they cause syzbot
failures might also make some maintainers react more..
Linus
