[LU-2964] lustre build fails on sles11sp2 Created: 14/Mar/13  Updated: 29/Jan/22  Resolved: 29/Jan/22

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Bob Glossman (Inactive) Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None
Environment:

sles11sp2, 3.0 kernel


Issue Links:
Duplicate
duplicates LU-2748 OSD uses kmalloc with high order to a... Resolved
Severity: 3
Rank (Obsolete): 7228

 Description   

Recent commit d7ac66d2fddc3b2a6fb91b6421f9a15b80c8d10a, LU-2748 osd: allocate buffers on demand, has broken the lustre server build on sles11sp2. errors:

  CC [M]  /home/bogl/lustre-release/lustre/lvfs/fsfilt-ldiskfs.o
/home/bogl/lustre-release/lustre/lvfs/fsfilt-ldiskfs.c:518: error: conflicting types for ‘ldiskfs_map_inode_page’
/home/bogl/lustre-release/ldiskfs/ldiskfs/ldiskfs.h:2022: error: previous declaration of ‘ldiskfs_map_inode_page’ was here
make[8]: *** [/home/bogl/lustre-release/lustre/lvfs/fsfilt-ldiskfs.o] Error 1
rm /home/bogl/lustre-release/lustre/lvfs/fsfilt-ldiskfs.c
make[7]: *** [/home/bogl/lustre-release/lustre/lvfs] Error 2
make[6]: *** [/home/bogl/lustre-release/lustre] Error 2
make[5]: *** [_module_/home/bogl/lustre-release] Error 2
make[4]: *** [sub-make] Error 2
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/linux-3.0.58-0.6.6-obj/x86_64/default'
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

The new added call to ldiskfs_map_inode_page() takes 5 args in the 3.0 kernel in sles11sp2, not the 4 args used in the 2.6 kernel. Needs some autoconf mods and #ifdefs to adapt to different kernel versions.

I suspect the build on the 3.7 kernel in FC18 may be broken too.

This isn't a critical bug right now because we don't routinely enable server builds on sles11sp2 yet.



 Comments   
Comment by James A Simmons [ 14/Mar/13 ]

Yep. I posted a patch last night to address this. http://review.whamcloud.com/#change,5708. Need to do redo the patch tho in a better way as you can see from andreas comments.

Comment by Cory Spitz [ 30/May/18 ]

Old issue; it should probably be closed.

Generated at Sat Feb 10 01:29:47 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.