Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jordan Glover <Golden_Miller83@protonmail.ch>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard Snapshot `0.0.20191205` Available
Date: Wed, 11 Dec 2019 20:22:50 +0100	[thread overview]
Message-ID: <CAHmME9qY8i63u2Mxzhkf4ie2RW9Ku5rCd0aMuxB8utGvT__bxw@mail.gmail.com> (raw)
In-Reply-To: <d6oxUBUTOkqCrCBzL2cNsRFieVsCyW8xyJyZP4qv24E4PwTWauo1bKsMThdjCPJ54N7QYRuPMwY-Tzj_js-3w31RQzYyWp6s7dZZVXiLBTg=@protonmail.ch>

On Wed, Dec 11, 2019 at 8:13 PM Jordan Glover
<Golden_Miller83@protonmail.ch> wrote:
>
> On Friday, December 6, 2019 5:35 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> > Looks like an arch problem or a libnftnl problem. I've made a minimal
> > reproducer:
> >
> > printf 'filter\nCOMMIT\nraw\nCOMMIT\n*mangle\nCOMMIT\n' | sudo
> > iptables-nft-restore -n
> >
> > I filed a bug report on Arch: https://bugs.archlinux.org/task/64755
> > You can follow up with them.
>
> I tried to compile myself iptables 1.8.4 which is latest upstream version
> and have good and bad news:
>
> The good one is your minimal reproducer no longer causes segfault.
>
> The bad one is wg-quick still does:
>
> wg-quick[2325]: [#] iptables-restore -n
> audit[2326]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=2326 comm="iptables-restor" exe="/usr/bin/xtables-nft-multi" sig=11 res=1
> wg-quick[2325]: /usr/bin/wg-quick: line 29:  2326 Segmentation fault      (core dumped) "$@"
> kernel: show_signal_msg: 40 callbacks suppressed
> kernel: iptables-restor[2326]: segfault at 0 ip 000069bb4df13cc9 sp 0000716fcc5b9b30 error 4 in libnftnl.so.11.2.0[69bb4df11000+18000]
> kernel: Code: 15 5c 20 02 00 48 85 c0 74 07 48 89 00 48 89 40 08 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 fd 53 48 83 ec 08 <48> 8b 3f 48 8b 1f 48 39 fd 74 2f 0f 1f 40 00 48 8b 47 08 48 89 43
>
> Maybe upstream found and fixed some regression but still missed
> the other one.

Can you craft a new minimal reproducer?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-12-11 19:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 10:55 Jason A. Donenfeld
2019-12-06 15:10 ` Jordan Glover
2019-12-06 15:20   ` Jason A. Donenfeld
2019-12-06 15:36     ` Jordan Glover
2019-12-06 15:52       ` Jason A. Donenfeld
2019-12-06 16:23         ` Jordan Glover
2019-12-06 17:35           ` Jason A. Donenfeld
2019-12-11 19:13             ` Jordan Glover
2019-12-11 19:22               ` Jason A. Donenfeld [this message]
2019-12-05 10:57 Jason A. Donenfeld

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=CAHmME9qY8i63u2Mxzhkf4ie2RW9Ku5rCd0aMuxB8utGvT__bxw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=Golden_Miller83@protonmail.ch \
    --cc=wireguard@lists.zx2c4.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).