diff options
| author | Petr Mladek <pmladek@suse.com> | 2023-03-07 13:53:34 +0100 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2023-03-17 12:03:46 -1000 |
| commit | 4c0736a76a186e5df2cd2afda3e7a04d2a427d1b (patch) | |
| tree | ee9ee79f1bca32553a91018a05452421f98379ac /ipc | |
| parent | 60f540389a5d2df25ddc7ad511b4fa2880dea521 (diff) | |
| download | linux-stable-4c0736a76a186e5df2cd2afda3e7a04d2a427d1b.tar.gz linux-stable-4c0736a76a186e5df2cd2afda3e7a04d2a427d1b.tar.bz2 linux-stable-4c0736a76a186e5df2cd2afda3e7a04d2a427d1b.zip | |
workqueue: Warn when a rescuer could not be created
Rescuers are created when a workqueue with WQ_MEM_RECLAIM is allocated.
It typically happens during the system boot.
systemd switches the root filesystem from initrd to the booted system
during boot. It kills processes that block the switch for too long.
One of the process might be modprobe that tries to create a workqueue.
These problems are hard to reproduce. Also alloc_workqueue() does not
pass the error code. Make the debugging easier by printing an error,
similar to create_worker().
Signed-off-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions