From: Jakub Kicinski <kuba@kernel.org>
To: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>
Cc: netdev@vger.kernel.org, Igor Raits <igor@gooddata.com>,
Daniel Secik <daniel.secik@gooddata.com>,
Zdenek Pesek <zdenek.pesek@gooddata.com>
Subject: Re: [regresion] Dell's OMSA Systems Management Data Engine stuck after update from 6.8.y to 6.9.y (with bisecting)
Date: Thu, 30 May 2024 17:33:24 -0700 [thread overview]
Message-ID: <20240530173324.378acb1f@kernel.org> (raw)
In-Reply-To: <CAK8fFZ7MKoFSEzMBDAOjoUt+vTZRRQgLDNXEOfdCCXSoXXKE0g@mail.gmail.com>
On Thu, 30 May 2024 09:52:38 +0200 Jaroslav Pulchart wrote:
> However, reverting just the "use xarray iterator to implement
> rtnl_dump_ifinfo" change did not resolve the issue. Do you have any
> suggestions on what to try next and how to fix it?
The daemon must have rolled its own netlink parsing.
Could you try this?
diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
index 96accde527da..5fd06473ddd9 100644
--- a/net/ipv4/devinet.c
+++ b/net/ipv4/devinet.c
@@ -1912,6 +1912,8 @@ static int inet_dump_ifaddr(struct sk_buff *skb, struct netlink_callback *cb)
goto done;
}
done:
+ if (err == -EMSGSIZE && likely(skb->len))
+ err = skb->len;
if (fillargs.netnsid >= 0)
put_net(tgt_net);
rcu_read_unlock();
next prev parent reply other threads:[~2024-05-31 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 7:52 [regresion] Dell's OMSA Systems Management Data Engine stuck after update from 6.8.y to 6.9.y (with bisecting) Jaroslav Pulchart
2024-05-31 0:33 ` Jakub Kicinski [this message]
2024-05-31 6:48 ` Jaroslav Pulchart
2024-05-31 21:26 ` Jakub Kicinski
2024-06-01 6:51 ` Jaroslav Pulchart
2024-06-01 21:25 ` Jakub Kicinski
2024-06-02 5:35 ` Jaroslav Pulchart
2024-06-02 21:56 ` Jakub Kicinski
2024-06-03 5:44 ` Jaroslav Pulchart
2024-06-03 18:49 ` Jakub Kicinski
2024-06-04 5:57 ` Jaroslav Pulchart
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=20240530173324.378acb1f@kernel.org \
--to=kuba@kernel.org \
--cc=daniel.secik@gooddata.com \
--cc=igor@gooddata.com \
--cc=jaroslav.pulchart@gooddata.com \
--cc=netdev@vger.kernel.org \
--cc=zdenek.pesek@gooddata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.