From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: dsahern@gmail.com, stephen@networkplumber.org, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH iproute2-next] libnetlink: Fix wrong netlink header placement
Date: Thu, 8 Dec 2022 16:38:16 +0200 [thread overview]
Message-ID: <20221208143816.936498-1-idosch@nvidia.com> (raw)
The netlink header must be first in the netlink message, so move it
there.
Fixes: fee4a56f0191 ("Update kernel headers")
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
---
include/libnetlink.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/libnetlink.h b/include/libnetlink.h
index 4d9696efa253..c91a22314548 100644
--- a/include/libnetlink.h
+++ b/include/libnetlink.h
@@ -38,9 +38,9 @@ struct nlmsg_chain {
};
struct ipstats_req {
+ struct nlmsghdr nlh;
struct if_stats_msg ifsm;
char buf[128];
- struct nlmsghdr nlh;
};
extern int rcvbuf;
--
2.37.3
next reply other threads:[~2022-12-08 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 14:38 Ido Schimmel [this message]
2022-12-08 16:04 ` [PATCH iproute2-next] libnetlink: Fix wrong netlink header placement Jiri Pirko
2022-12-08 16:07 ` David Ahern
2022-12-08 16:30 ` patchwork-bot+netdevbpf
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=20221208143816.936498-1-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=dsahern@gmail.com \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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