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

Dealing with kernels that have lustre enabled already

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Rank (Obsolete):
      15743

      Description

      Now that the kernels that have lustre (from that staging tree at the moment) included grows and distributions that ship it increase, we need to do something about all the problems this creates for us.

      Currently we cannot build our external lustre against such a kernel due to clash in config defines e.g.:

      make[1]: Entering directory `/home/green/bk/x86'
        CC [M]  /home/green/git/lustre-current/libcfs/libcfs/linux/linux-tracefile.o
      In file included from <command-line>:0:0:
      /home/green/git/lustre-current/config.h:26:0: error: "CONFIG_LNET_MAX_PAYLOAD" redefined [-Werror]
       #define CONFIG_LNET_MAX_PAYLOAD LNET_MTU
       ^
      In file included from /home/green/bk/linux/include/linux/kconfig.h:4:0,
                       from <command-line>:0:
      include/generated/autoconf.h:1571:0: note: this is the location of the previous definition
       #define CONFIG_LNET_MAX_PAYLOAD 1048576
       ^
      cc1: all warnings being treated as errors
      

      Once the lustre is moved out of staging tree, another problem will be added - clashing of symbols from lustre includes in the kernel tree (now hidden in secluded staging location so not a problem immediately).

      Once the config symbols clash is resolved - the other problem is the clash in module names between in-kernel lustre and out of kernel lustre. Due to in-kernel implementation mostly being geared towards clients and also lacking our debugging aids and such - these modules are not interchangeable really and we need to do something about it too - possibly consider renaming our out of tree modules? This will become a problem once distributions start to enable lustre by default in their kernels (so not a big problem yet too).

      Finally there are bound to be symbol clashes between in and out-of kernel lustre modules so we need to do something about that too I suspect, but not sure what so far. A wrapper to change the name a bit?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dmiter Dmitry Eremin (Inactive)
                Reporter:
                green Oleg Drokin
              • Votes:
                1 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: