From: Samuel Holland <samuel@sholland.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Kernel warning from WireGuard module
Date: Wed, 2 Nov 2016 01:12:07 -0500 [thread overview]
Message-ID: <b63711bd-0e64-767e-4b8e-310a7e2c6285@sholland.org> (raw)
In-Reply-To: <CAHmME9pidMFxVh9CaVWS0PHyyzzNZrNAqdBT43Mmk80WzU00+g@mail.gmail.com>
Hello,
On 11/02/2016 12:39 AM, Jason A. Donenfeld wrote:
> I believe it's fixed now with the current commits in master. I'll tag
> a new snapshot if the problems go away.
Great. I don't think it caused any noticeable side-effects; I just saw
the warning.
> My question still stands, though -- is this issue repeatable, or was
> it a one-off event?
It was just something I happened to notice in dmesg. I don't know if it
has happened before because I only recently started logging kernel
messages to disk on that machine. I do note that the warning is
WARN_ON_ONCE, so it will only show up in logs once per boot.
> Thanks,
> Jason
Thanks,
Samuel
prev parent reply other threads:[~2016-11-02 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 16:10 Samuel Holland
2016-11-01 18:41 ` Jason A. Donenfeld
2016-11-02 5:39 ` Jason A. Donenfeld
2016-11-02 6:12 ` Samuel Holland [this message]
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=b63711bd-0e64-767e-4b8e-310a7e2c6285@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 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).