All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Holland <samuel@sholland.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Instability during large transfers
Date: Fri, 17 Feb 2017 11:37:56 -0600	[thread overview]
Message-ID: <9f6ca811-e37e-4b5d-5685-c12ba9a8b667@sholland.org> (raw)
In-Reply-To: <CAHmME9qUBMh7DWwWboABv=oLXyfAq9-HWF93s4siPRfgzZpbBw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Hello,

On 02/17/17 07:36, Jason A. Donenfeld wrote:
> 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.

There do not appear to be any relevant changes to padata in the past few
years, and grsecurity doesn't look like it affects padata much, but that
doesn't rule it out:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=padata
https://grsecurity.net/changelog-test.txt

> I presume you have most PaX options turned on?

Attached is my config.gz (it's the same on all machines).

> Thanks,
> Jason

Thanks,
Samuel


[-- Attachment #2: config-4.7.10-hardened.gz --]
[-- Type: application/gzip, Size: 26725 bytes --]

  reply	other threads:[~2017-02-17 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 18:38 Instability during large transfers Samuel Holland
2017-02-17  4:48 ` Samuel Holland
2017-02-17 13:36   ` Jason A. Donenfeld
2017-02-17 17:37     ` Samuel Holland [this message]
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=9f6ca811-e37e-4b5d-5685-c12ba9a8b667@sholland.org \
    --to=samuel@sholland.org \
    --cc=Jason@zx2c4.com \
    --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 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.