[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2sqyjsod2s6kdukgipgcpjqdoysaw6trpgymxci36lmi3gykvx@tvg4qh3veuiq>
Date: Mon, 1 Dec 2025 22:06:24 +0000
From: Andre Carvalho <asantostc@...il.com>
To: Breno Leitao <leitao@...ian.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Shuah Khan <shuah@...nel.org>,
Simon Horman <horms@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net-next v8 4/5] netconsole: resume previously
deactivated target
On Mon, Dec 01, 2025 at 03:35:04AM -0800, Breno Leitao wrote:
> might hit a similar problem to the one fixed by e5235eb6cfe0 ("net:
> netpoll: initialize work queue before error checks")
>
> The code path would be:
> * alloc_param_target()
> * alloc_and_init()
> * kzalloc() fails and return NULL.
> * resume_wq() is still not initialized
> fail:
> * free_param_target()
> * cancel_work_sync(&nt->resume_wq); and resume_wq is not
> initialized
Checking this a bit now and I'm not sure if we have the same problem. On
alloc_param_target() the cleanup is simply kfree(nt).
free_param_target() is only called as part of netconsole module setup/cleanup but
only for targets that were succesfully added to the target list (so are guaranteed
to have resume_wq initialised) before we hit the error.
Let me know if I'm missing something!
--
Andre Carvalho
Powered by blists - more mailing lists