wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: Jaap Buurman <jaapbuurman@gmail.com>,
	openwrt-devel@lists.openwrt.org,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard & hw flow offload incompatibility
Date: Tue, 29 May 2018 14:38:42 +0200	[thread overview]
Message-ID: <CAHmME9oyNvnU4-2tZ9u7zp21_HigWH5_MFbu=Gb=jPe48kxpLA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9o3M+06Q1NDuhAD-oNwfwxuDU3G8eCwgsn4Gu0jjzZpMg@mail.gmail.com>

Hey Felix,

Per the below thread, I've been digging around trying to see what's
going on. Apparently packets are hitting a virtual network interface's
ndo_start_xmit with no dst when hardware offloading enabled. I assume
that the path is something along the lines of a packet coming in on
one of these hardware accelerated NICs and then being forwarded to the
wireguard interface, which expects the dst. I found your
ndo_flow_offload patchset, and I suspect that might have something to
do with this. Any insights on dsts disappearing in skbs?

Thanks,
Jason

On Tue, May 29, 2018 at 2:14 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote=
:
> Hi Jaap,
>
> Thanks for the clarification. I downloaded the binary for that
> hardware and triaged where the bug occurs [1]. This patch [2] should
> probably fix it, but I'm rather surprised to see situations in which a
> skb is missing a dst entry in ndo_start_xmit; this might point to
> deeper kernel bugs in this hardware offloading feature, or some
> alternative mechanism for routing being used when hardware offloading
> is on. So I'm hesitant to merge this just yet, because perhaps this is
> better handled in the compat layer, if it is in fact vendor silliness.
> Do you have a link to the kernel source of these boxes? I'd like to
> see what exactly the vendor is doing. And if you could try [2] and see
> if that still crashes, this would be most appreciated.
>
> Thanks,
> Jason
>
> [1] https://data.zx2c4.com/openwrt-mips-offloading-bug.png
> [2] https://=D7=90.cc/Am4tZ0n8
>
> On Tue, May 29, 2018 at 1:59 PM, Jaap Buurman <jaapbuurman@gmail.com> wro=
te:
>> Dear Jason,
>>
>> This isn't a regression. This is simply the first time this has been
>> observed. (hw) flow offload is a new feature, and hence this
>> interaction with wireguard is also new.
>>
>> Yours sincerely,
>>
>> Jaap
>>
>> On Tue, May 29, 2018 at 1:54 PM, Jason A. Donenfeld <Jason@zx2c4.com> wr=
ote:
>>> Hi Jaap,
>>>
>>> Thanks for the report. Is this a _new_ bug in _new_ version of
>>> WireGuard that wasn't there before. Or is this the first time you've
>>> observed this?
>>>
>>> Thanks,
>>> Jason
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Original Mail =3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
>
>> Dear all,
>>
>> When running a wireguard interface on the latest Lede master branch,
>> the router will crash as soon as traffic hits the wireguard interface
>> while (hw) flow offloading is enabled. I am not sure whether this is a
>> bug with wireguard, hw flow offload, both or neither, so I am
>> reporting the bug to both mailinglists. A more detailed description
>> plus a properly formatted stack trace can be found on Lede's bug
>> tracker: https://bugs.openwrt.org/index.php?do=3Ddetails&task_id=3D1539
>>
>> If you require any additional information, please do not hesitate to
>> contact me. Thank you very much in advance.
>>
>> Yours sincerely,
>>
>> Jaap Buurman

  reply	other threads:[~2018-05-29 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29  8:03 Wireguard & hw flow offload incompatibility Jaap Buurman
2018-05-29 11:54 ` Jason A. Donenfeld
2018-05-29 11:59   ` Jaap Buurman
2018-05-29 12:14     ` Jason A. Donenfeld
2018-05-29 12:38       ` Jason A. Donenfeld [this message]
2018-05-29 13:26         ` Jaap Buurman
2018-05-31  1:14           ` 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='CAHmME9oyNvnU4-2tZ9u7zp21_HigWH5_MFbu=Gb=jPe48kxpLA@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=jaapbuurman@gmail.com \
    --cc=nbd@nbd.name \
    --cc=openwrt-devel@lists.openwrt.org \
    --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).