From: Paolo Abeni <pabeni@redhat.com>
To: Breno Leitao <leitao@debian.org>,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com
Cc: thepacketgeek@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Aijay Adams <aijay@meta.com>
Subject: Re: [PATCH net-next] net: netconsole: Populate dynamic entry even if netpoll fails
Date: Tue, 13 Aug 2024 13:55:27 +0200 [thread overview]
Message-ID: <6185be94-65b9-466d-ad1a-bded0e4f8356@redhat.com> (raw)
In-Reply-To: <20240809161935.3129104-1-leitao@debian.org>
On 8/9/24 18:19, Breno Leitao wrote:> @@ -1304,8 +1308,6 @@ static int
__init init_netconsole(void)
> while ((target_config = strsep(&input, ";"))) {
> nt = alloc_param_target(target_config, count);
> if (IS_ERR(nt)) {
> - if (IS_ENABLED(CONFIG_NETCONSOLE_DYNAMIC))
> - continue;
> err = PTR_ERR(nt);
> goto fail;
> }
AFAICS the above introduces a behavior change: if
CONFIG_NETCONSOLE_DYNAMIC is enabled, and the options parsing fails for
any targets in the command line, all the targets will be removed.
I think the old behavior is preferable - just skip the targets with
wrong options.
Side note: I think the error paths in __netpoll_setup() assume the
struct netpoll will be freed in case of error, e.g. the device refcount
is released but np->dev is not cleared, I fear we could hit a reference
underflow on <setup error>, <disable>
Paolo
next prev parent reply other threads:[~2024-08-13 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 16:19 Breno Leitao
2024-08-13 11:55 ` Paolo Abeni [this message]
2024-08-13 15:57 ` Breno Leitao
2024-08-14 10:06 ` Paolo Abeni
2024-08-15 13:46 ` Breno Leitao
2024-08-15 16:07 ` Paolo Abeni
2024-08-15 17:16 ` Breno Leitao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6185be94-65b9-466d-ad1a-bded0e4f8356@redhat.com \
--to=pabeni@redhat.com \
--cc=aijay@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thepacketgeek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®