From: Mason <slash.tmp@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] package/linux-fusion: 'struct msghdr' has no member named 'msg_iov'
Date: Wed, 6 Jan 2016 17:35:22 +0100 [thread overview]
Message-ID: <568D424A.8060500@free.fr> (raw)
In-Reply-To: <568BBD3F.2030607@free.fr>
On 05/01/2016 13:55, Mason wrote:
> The linux-fusion package fails to build with recent kernels.
There is also an issue /loading/ the module.
# modprobe fusion
[ 49.971930] fusion: Unknown symbol tasklist_lock (err 0)
The tasklist_lock export was removed in 2.6.18
Kernel commit c59923a15c12d2b3597af913bf234a0ef264a38b
The actual issue was fixed in 2010, but returned in 3.19
because TREE_PREEMPT_RCU was renamed to PREEMPT_RCU.
The long-term fix seems to be along these lines:
diff --git a/linux/drivers/char/fusion/fusionee.c b/linux/drivers/char/fusion/fusionee.c
index ef067f5bc831..adaabaedb355 100644
--- a/linux/drivers/char/fusion/fusionee.c
+++ b/linux/drivers/char/fusion/fusionee.c
@@ -925,7 +925,7 @@ fusionee_kill(FusionDev * dev,
if (f != fusionee && (!target || target == f->id)) {
struct task_struct *p;
-#if defined(CONFIG_TREE_RCU) || defined(CONFIG_TREE_PREEMPT_RCU) || defined(CONFIG_TINY_RCU) || defined(rcu_read_lock)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,18) || defined(rcu_read_lock)
rcu_read_lock();
#else
read_lock(&tasklist_lock);
@@ -946,7 +946,7 @@ fusionee_kill(FusionDev * dev,
}
}
-#if defined(CONFIG_TREE_RCU) || defined(CONFIG_TREE_PREEMPT_RCU) || defined(CONFIG_TINY_RCU) || defined(rcu_read_unlock)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,18) || defined(rcu_read_lock)
rcu_read_unlock();
#else
read_unlock(&tasklist_lock);
next prev parent reply other threads:[~2016-01-06 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 12:55 [Buildroot] package/linux-fusion: 'struct msghdr' has no member named 'msg_iov' Mason
2016-01-05 14:33 ` Mason
2016-01-06 13:09 ` Mason
2016-01-06 16:35 ` Mason [this message]
2016-01-12 15:10 ` Mason
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=568D424A.8060500@free.fr \
--to=slash.tmp@free.fr \
--cc=buildroot@busybox.net \
/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