From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Frank Behrens <frank@harz.behrens.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard for FreeBSD without iflib
Date: Wed, 17 Mar 2021 16:17:59 -0600 [thread overview]
Message-ID: <CAHmME9qKqLnoFEJVk+3FH5Y7HM+6D=i6n=Ln4+HBntxjJpWWRw@mail.gmail.com> (raw)
In-Reply-To: <4621c1df-1fd0-489a-8a7d-b1731ae6626c@harz.behrens.de>
Hi Frank,
On Wed, Mar 17, 2021 at 1:29 PM Frank Behrens <frank@harz.behrens.de> wrote:
> I read your messages from the last days in the freebsd lists.
> In the version before removal from freebsd and in your current
> repository at https://git.zx2c4.com/wireguard-freebsd/ I see a problem.
> I can't load the module, because I get the error:
> Mar 17 20:07:53 <kern.crit> moon kernel: link_elf_obj: symbol
> qgroup_if_io_tqg undefined
> Mar 17 20:07:53 <kern.crit> moon kernel: linker_load_file:
> /usr/local/src/wg/src/if_wg.ko - unsupported file type
>
> I guess that is caused my the fact, that I do not have iflib in the
> kernel and you have only a TASKQGROUP_DECLARE(if_io_tqg) in the source
> and not TASKQGROUP_DEFINE(..).
Thanks for the report. Indeed it may yet take more time to clear out
all the iflib stuff.
Fixed here:
https://git.zx2c4.com/wireguard-freebsd/commit/?id=39c05742f16da7f71f4c781759a4b5135916a249
And this will be available in the next snapshot.
Jason
next prev parent reply other threads:[~2021-03-17 22:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 16:48 Removing WireGuard Support From FreeBSD Base Kyle Evans
2021-03-16 17:13 ` Jeffrey Walton
2021-03-16 17:37 ` Jason A. Donenfeld
2021-03-16 18:24 ` Nicolai
2021-03-16 17:30 ` Jason A. Donenfeld
2021-03-17 12:53 ` Gordon Bergling
2021-03-17 18:34 ` Jason A. Donenfeld
2021-03-17 19:29 ` Wireguard for FreeBSD without iflib Frank Behrens
2021-03-17 22:17 ` Jason A. Donenfeld [this message]
2021-03-19 7:47 ` Removing WireGuard Support From FreeBSD Base Gordon Bergling
2021-03-19 10:43 ` Evilham
2021-03-18 16:52 ` Kyle Evans
2021-03-18 16:57 ` 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='CAHmME9qKqLnoFEJVk+3FH5Y7HM+6D=i6n=Ln4+HBntxjJpWWRw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=frank@harz.behrens.de \
--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).