linux-kernel - Re: WARNING: at kernel/workqueue.c:1473 __queue

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200218163504.y5ofvaejleuf5tbh@ca-dmjordan1.us.oracle.com>
Date:   Tue, 18 Feb 2020 11:35:04 -0500
From:   Daniel Jordan <daniel.m.jordan@...cle.com>
To:     Corentin Labbe <clabbe.montjoie@...il.com>
Cc:     tj@...nel.org, jiangshanlai@...il.com, will@...nel.org,
        mark.rutland@....com, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0

Hi Corentin,

On Mon, Feb 17, 2020 at 09:48:03PM +0100, Corentin Labbe wrote:
> When running some CI test jobs (targeting crypto tests), I always get the following WARNING:

Can you be more specific about which test triggers this?  I used the config
option you mention and failed to reproduce after doing the boot-time crypto
tests and running various tcrypt incantations.

> [    7.886361] ------------[ cut here ]------------
> [    7.886388] WARNING: CPU: 2 PID: 147 at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0
> [    7.886394] Modules linked in: ghash_generic
> [    7.886409] CPU: 2 PID: 147 Comm: modprobe Not tainted 5.6.0-rc1-next-20200214-00068-g166c9264f0b1-dirty #545

I was using just plain next-20200214.  Can't find 166c9264f0b1, what tag/branch
were you using exactly?

> So it seems that it is a "events" workqueue that hit this problem.

Looks like "schedule_work(&init_free_wq)" in do_init_module(), can't be sure
though.

thanks,
Daniel