From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Alexandre Karlov <bassbeat@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel panic on ARM
Date: Tue, 30 May 2017 14:00:06 +0200 [thread overview]
Message-ID: <CAHmME9ou95Lq=Dc86iCC7H1_N+oLckyM7Ngrv1hwOp=TarOkRQ@mail.gmail.com> (raw)
In-Reply-To: <987716C2-3ABE-4705-A7AA-98511627C777@gmail.com>
Hi Alexandre,
Could you compile with `make debug`, so that dmesg gets plenty of
debugging output? That will let me see if this is related to
handshakes or to transport messages. An initial theory, based on the
stacktrace there involving fmonty and such, is that the 32-bit
implementation of curve25519-donna uses a lot of stack space, and if
you're on a kernel that puts the softirq stack and the process stack
in the same place, this could be an issue. Also, would you mind
sending your kernel's .config?
Jason
next prev parent reply other threads:[~2017-05-30 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 8:59 Alexandre Karlov
2017-05-30 11:48 ` Jason A. Donenfeld
2017-05-30 11:57 ` Alexandre Karlov
2017-05-30 12:00 ` Jason A. Donenfeld [this message]
2017-05-30 12:45 ` Jason A. Donenfeld
2017-05-30 13:29 ` Alexandre Karlov
2017-05-30 16:04 ` Jason A. Donenfeld
2017-05-30 18:54 ` Alexandre Karlov
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='CAHmME9ou95Lq=Dc86iCC7H1_N+oLckyM7Ngrv1hwOp=TarOkRQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=bassbeat@gmail.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 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).