[lustre-discuss] Trying to compile lustre 2.8 against kernel 4.5

[E.S. Rosenberg]

In the end I used kernel 4.2.x since we don't have time or expertise to
permit us to take the risk of editing the lustre source.
I believe HEAD is actually compatible with newer kernels since someone else
on the list recently reported installing it on Ubuntu 16.04 which is kernel
4.4.x

Only one small thing needed to be changed for kernel 4.2.x though I expect
it was already done in HEAD I am still including it below.

Regards,
Eli

commit ea0e7ce4f5031de4dfa8598a3185dca40ca175c5
Author: Keeper-of-the-Keys <esr+lustre at mail.hebrew.edu>
Date:   Tue May 31 20:43:22 2016 +0300

    asm/i387.h was renamed fpu/api.h as described here:

https://github.com/torvalds/linux/commit/df6b35f409af0a8ff1ef62f552b8402f3fef8665

diff --git a/libcfs/libcfs/linux/linux-crypto-crc32c-pclmul.c
b/libcfs/libcfs/linux/linux-crypto-crc32c-pclmul.c
index 9858db4..3c707bf 100644
--- a/libcfs/libcfs/linux/linux-crypto-crc32c-pclmul.c
+++ b/libcfs/libcfs/linux/linux-crypto-crc32c-pclmul.c
@@ -30,7 +30,7 @@
 #include <crypto/internal/hash.h>
 #include <linux/crc32.h>
 #include <asm/cpufeature.h>
-#include <asm/i387.h>
+#include <asm/fpu/api.h>
 #include <libcfs/libcfs.h>

 #define CHKSUM_BLOCK_SIZE      1


On Mon, May 23, 2016 at 5:41 AM, Drokin, Oleg <oleg.drokin at intel.com> wrote:

> Hello!
>
> On May 22, 2016, at 2:38 PM, E.S. Rosenberg wrote:
>
> > Internal functions have changed and as a result it is currently not
> compiling, what is the accepted style for fixing these things?
> >
> > Right now I am looking at this error:
> > lustre-release/lustre/fid/lproc_fid.c: In function
> ‘lprocfs_client_fid_space_seq_show’:
> > lustre-release/lustre/fid/lproc_fid.c:542:5: error: void value not
> ignored as it ought to be
> >   rc = seq_printf(m, "["LPX64" - "LPX64"]:%x:%s\n",
> >
> > which may be straight forward to fix or may not be depending on how
> lprocfs_client_fid_space_seq_show is used.
> >
> > seq_printf used to return 0 or -1 which would in turn be returned by
> this function, now seq_printf does not return anything anymore.
>
> Just open a ticket in jira.hpdd.intel.com describing the problem either
> especifically for every problem, or in general like "support for Linux
> kernel 4.5"
> Then submit patch to review.hpdd.intel.com with the fix, reference the
> ticket.
> Don't forget to add necessary compat logic to configure and elsewhere when
> needed (though I guess we can just irnore return value from
> seq_printf everywhere with no ill effects?
>
> See https://wiki.hpdd.intel.com/display/PUB/Submitting+Changes and
> https://wiki.hpdd.intel.com/display/PUB/Patch+Landing+Process+Summary
>
> Bye,
>     Oleg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20160623/70057b8e/attachment.htm>