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

Client support for upstream 3.8 kernel

Details

    • 6901

    Description

      Update client code to support upstream 3.8 kernel.

      Attachments

        Issue Links

          Activity

            [LU-2850] Client support for upstream 3.8 kernel

            Peter can you label this as a 2.5 item

            simmonsja James A Simmons added a comment - Peter can you label this as a 2.5 item
            pjones Peter Jones added a comment -

            Alexey

            2.4.0 is frozen now. This work will land in later releases

            Peter

            pjones Peter Jones added a comment - Alexey 2.4.0 is frozen now. This work will land in later releases Peter

            Are there plans to land all this patches before 2.4.0 release? Or they will be postponed to 2.4.x or 2.5.x?

            alexxy Alexey Shvetsov (Inactive) added a comment - Are there plans to land all this patches before 2.4.0 release? Or they will be postponed to 2.4.x or 2.5.x?

            BTW for 3.9 kernel support. Patches may be simplyfyed if stuff for ancient kernels (<2.6.32) will be cleaned up. See LU-2800

            alexxy Alexey Shvetsov (Inactive) added a comment - BTW for 3.9 kernel support. Patches may be simplyfyed if stuff for ancient kernels (<2.6.32) will be cleaned up. See LU-2800
            ys Yang Sheng added a comment -

            I tend to waiting patches landed and then rebase lu-3079.

            ys Yang Sheng added a comment - I tend to waiting patches landed and then rebase lu-3079.
            simmonsja James A Simmons added a comment - - edited

            I noticed that the 5655 patch is not dependent on any other patches. This is fine but I noticed the patches in LU-3079 don't apply cleanly due to the other patches here. Should we just want until a few patches land then rebase the patches in LU-3079 again or make 5655 dependent on the rest of the series in this ticket?

            simmonsja James A Simmons added a comment - - edited I noticed that the 5655 patch is not dependent on any other patches. This is fine but I noticed the patches in LU-3079 don't apply cleanly due to the other patches here. Should we just want until a few patches land then rebase the patches in LU-3079 again or make 5655 dependent on the rest of the series in this ticket?
            bergwolf Peng Tao added a comment -

            James, please upload it. It helps avoiding dup efforts. Thanks.

            Yang, sorry for not including you in the first place. Will add you as inspector in all my future kernel support patches.

            bergwolf Peng Tao added a comment - James, please upload it. It helps avoiding dup efforts. Thanks. Yang, sorry for not including you in the first place. Will add you as inspector in all my future kernel support patches.

            I have a update rebased for 5655 if you want me to upload it.

            simmonsja James A Simmons added a comment - I have a update rebased for 5655 if you want me to upload it.

            Seems current list are for kernel v3.8
            http://review.whamcloud.com/4649
            http://review.whamcloud.com/5973
            http://review.whamcloud.com/5974
            http://review.whamcloud.com/5768
            http://review.whamcloud.com/5781
            http://review.whamcloud.com/5763
            http://review.whamcloud.com/5613
            http://review.whamcloud.com/5655
            Last one need a rebase it conflicts with current master and this patches

            LU-2850 kernel: 3.8 upstream kills daemonize()

            kernel_thread() is a low level kernel function.
            Instead of calling kernel_thread() and relying on daemonize()
            to create new kernel threads, we should really switch to
            kthread_run() and elimilate daemonize().

            Conflicts:
            libcfs/autoconf/lustre-libcfs.m4
            lustre/mdd/mdd_lfsck.c
            lustre/obdclass/llog_cat.c
            lustre/ptlrpc/recov_thread.c

            Also patches that good to have in 2.4 are
            http://review.whamcloud.com/6064 <- fix compilation with gcc-4.7.x gcc-4.8.x
            http://review.whamcloud.com/5960 <- fix for zfs-0.6.1
            http://review.whamcloud.com/5751 <- possible fix for sandbox enabled build systems

            alexxy Alexey Shvetsov (Inactive) added a comment - Seems current list are for kernel v3.8 http://review.whamcloud.com/4649 http://review.whamcloud.com/5973 http://review.whamcloud.com/5974 http://review.whamcloud.com/5768 http://review.whamcloud.com/5781 http://review.whamcloud.com/5763 http://review.whamcloud.com/5613 http://review.whamcloud.com/5655 Last one need a rebase it conflicts with current master and this patches LU-2850 kernel: 3.8 upstream kills daemonize() kernel_thread() is a low level kernel function. Instead of calling kernel_thread() and relying on daemonize() to create new kernel threads, we should really switch to kthread_run() and elimilate daemonize(). Conflicts: libcfs/autoconf/lustre-libcfs.m4 lustre/mdd/mdd_lfsck.c lustre/obdclass/llog_cat.c lustre/ptlrpc/recov_thread.c Also patches that good to have in 2.4 are http://review.whamcloud.com/6064 <- fix compilation with gcc-4.7.x gcc-4.8.x http://review.whamcloud.com/5960 <- fix for zfs-0.6.1 http://review.whamcloud.com/5751 <- possible fix for sandbox enabled build systems
            ys Yang Sheng added a comment -

            Oops, Please give me a chance be a inspector for kernel update relate patches. So avoid dup efforts. Thanks.

            ys Yang Sheng added a comment - Oops, Please give me a chance be a inspector for kernel update relate patches. So avoid dup efforts. Thanks.
            ys Yang Sheng added a comment - http://review.whamcloud.com/6114

            People

              ys Yang Sheng
              bergwolf Peng Tao
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: