It seems some of our customers/users are building Lustre with a lot more restrictive gcc options than we are (e.g see http://review.whamcloud.com/#/c/13654/1)

To avoid such things in the future, we really need to be building Lustre with the most protections and checks allowed by a particular compiler being used (need to detect this in configure somehow).
We'll also need to do it twice - once for the kernel where we are more restricted to remain compatible with the rest of the kernel,
and another time for our userspace tools and libraries - there we probably need to go full in with all the checks.