From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Ed Maste <emaste@freebsd.org>
Cc: Michael Pro <michael.adm@gmail.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>,
Kyle Evans <kevans@freebsd.org>
Subject: Re: FreeBSD current socket-src changed. Wireguard not compiling.
Date: Sun, 4 Sep 2022 19:20:43 +0200 [thread overview]
Message-ID: <CAHmME9rN=kqPz0KgWUyhQ=4q=HLwkUL8cSXTnJ5ySmdgs4N8Xg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oqxSuV2b4ZtHqenscfJfWi72mcQgebDi2pgTT7n_62Ng@mail.gmail.com>
On Sun, Sep 4, 2022 at 7:07 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi Ed,
>
> On Wed, Aug 31, 2022 at 8:18 PM Ed Maste <emaste@freebsd.org> wrote:
> >
> > On Mon, 29 Aug 2022 at 12:18, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > > On Tue, Aug 23, 2022 at 12:26:21PM +0300, Michael Pro wrote:
> > > > Tonight after updating kernel freebsd current I got coredump with
> > > > wireguard enabled kernel module.
> > > > ...
> > > Thanks. Is there a __FreeBSD_version__ change that corresponds?
> >
> > It is not an exact match, but was bumped to 1400066 shortly after and
> > should be a suitable value to check.
>
> Thanks.
>
> Michael - could you give this a try?
> https://git.zx2c4.com/wireguard-freebsd/commit/?id=89b7292797c17449e24f5b8b08cb2412a51d2484
Err, that would be the wrong code copy&paste. This, I meant:
https://git.zx2c4.com/wireguard-freebsd/commit/?id=20584d1c329ed2a71893375fa11ca4c56ed9f642
prev parent reply other threads:[~2022-09-04 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 9:26 Michael Pro
2022-08-29 16:16 ` Jason A. Donenfeld
2022-08-31 18:18 ` Ed Maste
2022-09-01 5:40 ` Michael Pro
2022-09-04 17:07 ` Jason A. Donenfeld
2022-09-04 17:20 ` Jason A. Donenfeld [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='CAHmME9rN=kqPz0KgWUyhQ=4q=HLwkUL8cSXTnJ5ySmdgs4N8Xg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=emaste@freebsd.org \
--cc=kevans@freebsd.org \
--cc=michael.adm@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).