From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Samuel Holland <samuel@sholland.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Instability during large transfers
Date: Fri, 17 Feb 2017 14:36:22 +0100 [thread overview]
Message-ID: <CAHmME9qUBMh7DWwWboABv=oLXyfAq9-HWF93s4siPRfgzZpbBw@mail.gmail.com> (raw)
In-Reply-To: <05adeaed-20ff-ce42-b8c6-73bbc55d7021@sholland.org>
Hey Samuel,
Thanks very much for the excellent debugging output. I'll try to
reproduce this as well on my systems.
The stack trace does indicate that the OOPS is happening in padata,
not in wireguard, so I wonder if this is some bug caused either by
grsecurity or by something else that was then fixed, but since your
kernel is a bit old (4.7.10) maybe the fix didn't make it. In either
case, I'll try to reproduce on that kernel and on newer kernels and
will get back to you.
I presume you have most PaX options turned on?
Thanks,
Jason
next prev parent reply other threads:[~2017-02-17 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 18:38 Samuel Holland
2017-02-17 4:48 ` Samuel Holland
2017-02-17 13:36 ` Jason A. Donenfeld [this message]
2017-02-17 17:37 ` Samuel Holland
2017-03-01 22:44 ` Samuel Holland
2017-03-21 15:06 ` Samuel Holland
2017-03-21 17:33 ` 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='CAHmME9qUBMh7DWwWboABv=oLXyfAq9-HWF93s4siPRfgzZpbBw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=samuel@sholland.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).