All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Bercot <ska-devel@skarnet.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables: nft fails to add rules to chains
Date: Sun, 22 Mar 2015 19:45:18 +0100	[thread overview]
Message-ID: <550F0DBE.7000905@skarnet.org> (raw)
In-Reply-To: <20150322183106.GA4150@salvia>

  Hi Pedro,

  Thanks for answering.
  Patch applied, and as expected nft now fails with the messages

libnftnl: Expression 'payload' not supported
netlink.c:182: Memory allocation failure


> I think this error is bogus. Please, apply this patch to libnftnl and
> let us know.  For some reason __init is being ignored, are you using
> gcc?

  I am using gcc (version 4.8.3). However I am not using glibc, but musl,
and I link statically. This is probably the main difference between my
system and the ones you guys are used to.
  Is the "constructor" gcc attribute incompatible with static linking ?
Or is nft using glibc-specific constructs ?

-- 
  Laurent


  reply	other threads:[~2015-03-22 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 20:24 nftables: nft fails to add rules to chains Laurent Bercot
2015-03-21 20:16 ` Laurent Bercot
2015-03-22 18:31 ` Pablo Neira Ayuso
2015-03-22 18:45   ` Laurent Bercot [this message]
2015-03-22 18:47     ` Laurent Bercot
2015-03-22 19:00     ` Pablo Neira Ayuso
2015-03-22 19:00       ` Laurent Bercot
2015-03-23 11:45         ` Pablo Neira Ayuso
2015-03-23 13:32           ` nftables feature request: don't fail "flush" on nonexistent tables (was: nftables: nft fails to add rules to chains) Laurent Bercot
2015-03-23 19:42             ` Arturo Borrero Gonzalez
2015-03-24 10:06               ` nftables feature request: don't fail "flush" on nonexistent tables Laurent Bercot

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=550F0DBE.7000905@skarnet.org \
    --to=ska-devel@skarnet.org \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.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 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.