From: Christian Kuntz <c.kuntz@opendrives.com>
To: Lustre-devel <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] zfs module taints osd_zfs and causes modprobe to fail
Date: Thu, 29 Jul 2021 16:31:44 -0700 [thread overview]
Message-ID: <CANdLGj6GDFX08SqsseGDej7xHDLWvA=95gnUhNuh0jjkJxGnkw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1354 bytes --]
Hi all,
Resident crazy guy Christian here, I'm compiling lustre 2.14 on kernel
4.19.194 with ZFS 2.0.3 and running into a bit of a challenge thanks to this
kernel commit
<https://github.com/torvalds/linux/commit/262e6ae7081df304fc625cf368d5c2cbba2bb991>
.
In short, `modprobe lustre` succeeds but `modprobe osd_zfs` fails and
generates this output in dmesg:
[82645.937126] osd_zfs: module_layout: kernel tainted.
[82645.937526] osd_zfs: module uses symbols from proprietary module zfs,
inheriting taint.
[82645.938356] osd_zfs: Unknown symbol ktime_get_real_seconds (err -2)
[82645.938568] osd_zfs: Unknown symbol ktime_get_seconds (err -2)
From what I can gather, the license taint from zfs floats up to osd_zfs,
and since osd_zfs becomes tainted as a non-GPL module it can no longer
utilize the GPL-only symbols from ktime, causing the module insertion to
fail.
As far as I can tell, my options are to either patch the taint inheritance
out of the kernel, add new functions to osd_zfs that replace the
functionality of ktim_get_real_seconds and ktime_get_seconds (honestly,
that feels a bit intimidating), or remove the gpl only requirement from
osd_zfs. Has anyone else run into this and found working solutions yet?
Cheers,
Christian
--
<https://opendrives.ac-page.com/nabshow2021?utm_source=emailsig&utm_medium=email&utm_campaign=NAB2021>
[-- Attachment #1.2: Type: text/html, Size: 1680 bytes --]
[-- Attachment #2: Type: text/plain, Size: 165 bytes --]
_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
reply other threads:[~2021-07-29 23:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANdLGj6GDFX08SqsseGDej7xHDLWvA=95gnUhNuh0jjkJxGnkw@mail.gmail.com' \
--to=c.kuntz@opendrives.com \
--cc=lustre-devel@lists.lustre.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).