From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, alialnu@nvidia.com, stable@dpdk.org
Subject: Re: [PATCH] net/tap: fix build with LTO
Date: Mon, 22 Sep 2025 20:57:07 -0700 [thread overview]
Message-ID: <20250922205707.5beb72e5@hermes.local> (raw)
In-Reply-To: <20250922073043.2394557-1-david.marchand@redhat.com>
On Mon, 22 Sep 2025 09:30:43 +0200
David Marchand <david.marchand@redhat.com> wrote:
> The compiler has trouble understanding that the code is actually pointing
> at the data in the message past the nh struct.
>
> Update the tap_nlattr_add* helpers and the NLMSG_TAIL macro passing a
> pointer to msg.
>
> Bugzilla ID: 1511
> Fixes: 7c25284e30c2 ("net/tap: add netlink back-end for flow API")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Queued to next-net.
Other drivers that still have outstanding LTO issues
are: mlx5, cnxk, bnxt
prev parent reply other threads:[~2025-09-23 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:30 David Marchand
2025-09-22 22:12 ` Stephen Hemminger
2025-09-23 3:57 ` Stephen Hemminger [this message]
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=20250922205707.5beb72e5@hermes.local \
--to=stephen@networkplumber.org \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).