https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-5322 Lustre <p>tracker for 3.16 kernel support<br/> all mods for kernel versions &gt; 3.14 should be collected here</p> <p>fc20 recently bumped their kernel version from 3.14.x to 3.15.x<br/> new build failures are now showing up</p> <p>Some issues already mentioned in comments in <a href="https://jira.whamcloud.com/browse/LU-4993" title="support for 3.14 linux kernel" class="issue-link" data-issue-key="LU-4993"><del>LU-4993</del></a></p> fc20 LU-5322

support for 3.16 linux kernel

Improvement Minor Resolved Fixed Bob Glossman Bob Glossman Thu, 10 Jul 2014 17:08:16 +0000 Thu, 19 Feb 2015 20:02:58 +0000 Wed, 18 Feb 2015 21:47:47 +0000 Lustre 2.7.0 0 5 <p><a href="http://review.whamcloud.com/#/c/11058" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/11058</a><br/> <a href="http://review.whamcloud.com/#/c/11059" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/11059</a></p> <p>Bob does this help ?</p> <p>James, Yes, that help's a lot. With those patches I can build client-only again in 3.15+. I will need to refresh the ldiskfs patches before I can build servers. Changes from the 3.12 reference set are a bit more than those I had for 3.14.</p> <p>fc20 just recently jumped from a 3.15.x kernels to 3.16.2-200.fc20. With the switch to 3.16 now seeing new build failures, even in client only builds. example errors:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> CC [M] /home/bogl/lustre-release/lustre/llite/llite_capa.o CC [M] /home/bogl/lustre-release/lustre/llite/rw26.o /home/bogl/lustre-release/lustre/llite/rw26.c:700:9: error: initialization from incompatible pointer type [-Werror] .direct_IO = ll_direct_IO_26, ^ /home/bogl/lustre-release/lustre/llite/rw26.c:700:9: error: (near initialization for ‘ll_aops.direct_IO’) [-Werror] cc1: all warnings being treated as errors make[6]: *** [/home/bogl/lustre-release/lustre/llite/rw26.o] Error 1 make[5]: *** [/home/bogl/lustre-release/lustre/llite] Error 2 make[4]: *** [/home/bogl/lustre-release/lustre] Error 2 make[3]: *** [_module_/home/bogl/lustre-release] Error 2 make[3]: Leaving directory `/usr/src/kernels/3.16.2-200.fc20.x86_64' make[2]: *** [modules] Error 2 make[2]: Leaving directory `/home/bogl/lustre-release' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/bogl/lustre-release' make: *** [all] Error 2 </pre> </div></div> <p>similar build failure also seen in fc21 alpha, just announced. it also has a 3.16 kernel, just like fc20.</p> <p>Patches landed to Master.</p> <p>Still experiencing the build failure described by Bob on 15/Sep/14 with today's master (commit: 4de90170e2573321e7691364d1d527aedfd25ff9). As far as I understand the problem in this case are the changes to VFS from Linux 3.15 to 3.16. Documentation/filesystems/vfs.txt demands the following signature for direct_IO:<br/> <tt>ssize_t (*direct_IO)(int, struct kiocb *, struct iov_iter *iter, loff_t offset);</tt> <br/> whereas rw26.c in master has <br/> <tt>static ssize_t ll_direct_IO_26(int rw, struct kiocb *iocb, const struct iovec *iov, loff_t file_offset, unsigned long nr_segs)</tt><br/> which is ok until including Kernel 3.15 but not anymore for 3.16.<br/> The upstream kernel lustre client has a matching function signature for it.</p> <p>Sorry I have been busy doing other clean ups. I plan to complete this for Lustre 2.8.</p> <p>please track issues for later lustre versions in <a href="https://jira.whamcloud.com/browse/LU-6260" title="more support for 3.16 linux kernel" class="issue-link" data-issue-key="LU-6260"><del>LU-6260</del></a></p> Related LU-4993 LU-5609 LU-6260 Development Rank 1|hzwr47: Rank (Obsolete) 14860