Re: [next] [arm64] [gpio] BUG: key has not been registered! DEBUG_LOCKS_WARN_ON:

From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Colin King <colin.king@canonical.com>,
	Christian Brauner <christian.brauner@ubuntu.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [next] [arm64] [gpio] BUG: key has not been registered! DEBUG_LOCKS_WARN_ON:
Date: Thu, 8 Apr 2021 01:51:28 +0300	[thread overview]
Message-ID: <CAHp75VdJ7kGXN6sk8HTeSfAKQtHDGSmtdVPn7CSkK5=yfDizuA@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYsiRYaE+y44ApDkvPvbDCdiJ+nnCMhiiaPVsg6p8m4+1Q@mail.gmail.com>

On Thu, Apr 8, 2021 at 12:38 AM Naresh Kamboju
<naresh.kamboju@linaro.org> wrote:
>
> While running kselftest recently added gpio gpio-sim.sh test case the following
> warning was triggered on Linux next tag 20210330 tag running on arm64 juno
> and hikey devices.
>
> GOOD: next-20210326
> BAD: next-20210330
>
> This is still happening today on Linux next tag 20210407.

Can you add the following

  sysfs_attr_init(attrs[i]);

to the end of the loop in gpio_sim_setup_sysfs()?

If it fixes an issue I'll send a formal patch.

-- 
With Best Regards,
Andy Shevchenko