[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKa-r6vJjeYqGZERRr=B4ykLf-efPRY3h=HU3y3QxazwZ_cMAg@mail.gmail.com>
Date: Tue, 30 Apr 2024 12:17:41 +0200
From: Davide Caratti <dcaratti@...hat.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: lkft-triage@...ts.linaro.org, regressions@...ts.linux.dev,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org, jhs@...atatu.com,
xiyou.wangcong@...il.com, jiri@...nulli.us, cpaasch@...le.com,
pabeni@...hat.com, xmu@...hat.com, maxim@...valent.com, edumazet@...gle.com,
anders.roxell@...aro.org, dan.carpenter@...aro.org, arnd@...db.de,
Linux Kernel Functional Testing <lkft@...aro.org>
Subject: Re: selftests: tc-testing: tdc.sh: WARNING: at kernel/locking/lockdep.c:1226
lockdep_register_key
hello,
On Tue, Apr 30, 2024 at 12:17 AM Naresh Kamboju
<naresh.kamboju@...aro.org> wrote:
>
> While running selftests: tc-testing: tdc.sh the following kernel warnings,
> kernel Bug, kernel oops and kernel panic noticed with Linux next-20240429
> tag kernel as per the available data.
>
> This build config is from kselftest merge config[1].
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> selftests: tc-testing: tdc.sh log and crash log
the problem is created by [1]. I think that at least we need to guard
against failures to allocate sch->cpu_bstats and sch->cpu_qstats,
otherwise the dynamic key is registered but never unregistered (though
the key is freed in the error path of of qdisc_alloc() ). But there
might be also something else; however, I can reproduce some similar
splat, will follow-up on the list.
sorry for the noise,
--
davide
[1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=af0cb3fa3f9ed258d14abab0152e28a0f9593084
Powered by blists - more mailing lists