On Wed, 17 Apr 2024 at 22:28, Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > > On Wed, 17 Apr 2024 13:46:36 -0700 Jakub Kicinski wrote: > > > I can spend some time on them after I verify that my fix for -stable > > > is actually fixing an issue I think it fixes. > > > Seems like your automation + my selftests are giving some fruits, hehe. > > > > Oh, very interesting, I don't recall these coming up before. > > Correction, these are old, and if I plug the branch names here: > https://netdev.bots.linux.dev/contest.html > there is a whole bunch of tests failing that day. Hmm, yeah, I was looking at the history of selftests to see if there is anything else interesting: 2024-04-11--15-00 - lockdep for hashinfo->ehash_locks vs tw->tw_timer It seems that you actually reported that already here: https://lore.kernel.org/all/20240411100536.224fa1e7@xxxxxxxxxx/ 2024-04-04--12-00 - lockdep for p->alloc_lock vs ul->lock (rt6_uncached_list_flush_dev) 2024-04-04--09-00 - lockdep for p->alloc_lock vs ndev->lock (addrconf_permanent_addr) 2024-04-04--03-00 - lockdep for p->alloc_lock vs ul->lock Was reported as well: https://lore.kernel.org/all/8576a80ac958812ac75b01299c2de3a6485f84a1.camel@xxxxxxxxxx/ 2024-03-06--00-00 - kernel BUG at net/core/skbuff.c:2813 Can't really track this down to any report/fix. Probably as it's month old and hasn't happened since on these tests - something was borken on that particular day. > Keep in mind these run pre-commit so not all failures are flakes. Thanks, Dmitry
