From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Eugene Syromyatnikov <evgsyr@gmail.com>,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: strace build error static assertion failed: "XFRM_MSG_MAPPING != 0x26"
Date: Thu, 7 Oct 2021 00:48:16 +0300 [thread overview]
Message-ID: <20211006214816.GA11000@altlinux.org> (raw)
In-Reply-To: <1eb25b8f-09c0-8f5e-3227-f0f318785995@alliedtelesis.co.nz>
On Wed, Oct 06, 2021 at 09:43:11PM +0000, Chris Packham wrote:
> Hi,
>
> When compiling strace-5.14 (although it looks like the same problem
> would exist with bleeding edge strace) with headers from the tip of
> Linus's tree (5.15.0-rc4) I get the following error
>
> strace: In file included from static_assert.h:11,
> strace: from print_fields.h:12,
> strace: from defs.h:1901,
> strace: from netlink.c:10:
> strace: xlat/nl_xfrm_types.h:162:1: error: static assertion failed:
> "XFRM_MSG_MAPPING != 0x26"
> strace: static_assert((XFRM_MSG_MAPPING) == (0x26), "XFRM_MSG_MAPPING
> != 0x26");
> strace: ^~~~~~~~~~~~~
>
> It looks like commit 2d151d39073a ("xfrm: Add possibility to set the
> default to block if we have no policy") added some XFRM messages and the
> numbers shifted. Is this considered an ABI breakage?
>
> I'm not sure if this is a strace problem or a linux problem so I'm
> reporting it in both places.
Yes, this is already covered by
https://lore.kernel.org/lkml/20210912122234.GA22469@asgard.redhat.com/T/#u
Thanks,
--
ldv
next prev parent reply other threads:[~2021-10-06 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 21:43 strace build error static assertion failed: "XFRM_MSG_MAPPING != 0x26" Chris Packham
2021-10-06 21:48 ` Dmitry V. Levin [this message]
2021-10-06 21:51 ` Dmitry V. Levin
2021-10-07 5:57 ` Steffen Klassert
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=20211006214816.GA11000@altlinux.org \
--to=ldv@altlinux.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=evgsyr@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).