Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-6264

Enable strict compiler defence modes

Details

    • Improvement
    • Resolution: Duplicate
    • Major
    • Lustre 2.8.0
    • None
    • None
    • 17558

    Description

      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.

      Attachments

        Issue Links

          Activity

            [LU-6264] Enable strict compiler defence modes

            Fixed with http://review.whamcloud.com/15392 "LU-6835 build: add -Wall to CFLAGS for test/ and utils/".

            adilger Andreas Dilger added a comment - Fixed with http://review.whamcloud.com/15392 " LU-6835 build: add -Wall to CFLAGS for test/ and utils/".

            With the patch from John Hammond for LU-6835 the compiler has strict defense mode for the user land code.

            simmonsja James A Simmons added a comment - With the patch from John Hammond for LU-6835 the compiler has strict defense mode for the user land code.
            green Oleg Drokin added a comment -

            Dmitry, can you please take at lest an initial stab at it?

            green Oleg Drokin added a comment - Dmitry, can you please take at lest an initial stab at it?

            People

              dmiter Dmitry Eremin (Inactive)
              green Oleg Drokin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: