linux-kernel - Re: [PATCH] ASoC: da7219: Initialize jack_det

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 08 Mar 2023 15:20:17 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Support Opensource <support.opensource@...semi.com>,
        Guenter Roeck <linux@...ck-us.net>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org,
        David Rau <David.Rau.opensource@...renesas.com>
Subject: Re: [PATCH] ASoC: da7219: Initialize jack_det_mutex

On Tue, 07 Mar 2023 07:51:11 -0800, Guenter Roeck wrote:
> The following traceback is reported if mutex debugging is enabled.
> 
> DEBUG_LOCKS_WARN_ON(lock->magic != lock)
> WARNING: CPU: 0 PID: 17 at kernel/locking/mutex.c:950 __mutex_lock_common+0x31c/0x11d4
> Modules linked in:
> CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 5.10.172-lockdep-21846-g849884cfca5a #1 fd2de466502012eb58bc8beb467f07d0b925611f
> Hardware name: MediaTek kakadu rev0/rev1 board (DT)
> Workqueue: events da7219_aad_jack_det_work
> pstate: 60400005 (nZCv daif +PAN -UAO -TCO BTYPE=--)
> pc : __mutex_lock_common+0x31c/0x11d4
> lr : __mutex_lock_common+0x31c/0x11d4
> sp : ffffff80c0317ae0
> x29: ffffff80c0317b50 x28: ffffff80c0317b20
> x27: 0000000000000000 x26: 0000000000000000
> x25: 0000000000000000 x24: 0000000100000000
> x23: ffffffd0121d296c x22: dfffffd000000000
> x21: 0000000000000000 x20: 0000000000000000
> x19: ffffff80c73d7190 x18: 1ffffff018050f52
> x17: 0000000000000000 x16: 0000000000000000
> x15: 0000000000000000 x14: 0000000000000000
> x13: 0000000000000001 x12: 0000000000000001
> x11: 0000000000000000 x10: 0000000000000000
> x9 : 83f0d991da544b00 x8 : 83f0d991da544b00
> x7 : 0000000000000000 x6 : 0000000000000001
> x5 : ffffff80c03176a0 x4 : 0000000000000000
> x3 : ffffffd01067fd78 x2 : 0000000100000000
> x1 : ffffff80c030ba80 x0 : 0000000000000028
> Call trace:
> __mutex_lock_common+0x31c/0x11d4
> mutex_lock_nested+0x98/0xac
> da7219_aad_jack_det_work+0x54/0xf0
> process_one_work+0x6cc/0x19dc
> worker_thread+0x458/0xddc
> kthread+0x2fc/0x370
> ret_from_fork+0x10/0x30
> irq event stamp: 579
> hardirqs last enabled at (579): [<ffffffd012442b30>] exit_to_kernel_mode+0x108/0x138
> hardirqs last disabled at (577): [<ffffffd010001144>] __do_softirq+0x53c/0x125c
> softirqs last enabled at (578): [<ffffffd01009995c>] __irq_exit_rcu+0x264/0x4f4
> softirqs last disabled at (573): [<ffffffd01009995c>] __irq_exit_rcu+0x264/0x4f4
> ---[ end trace 26da674636181c40 ]---
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: da7219: Initialize jack_det_mutex
      commit: af0f46e5b9a462aaa1d76e82781a5316f03828eb

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark