[Bug 99277] New: CONFIG_STACK_VALIDATION=y causes compilation from source of external drivers to fail

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99277

            Bug ID: 99277
           Summary: CONFIG_STACK_VALIDATION=y causes compilation from
                    source of external drivers to fail
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: tomasjonnes at outlook.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

After building the linux branch intel-drm-nightly kernel (4.10) with the
default values, booting the new kernel and trying to compile an external driver
( tested with several nvidia drivers, rtl8812AU-4.3.22 and bbswitch-0.8 ) from
source, the compilation process will try to link the object files before even
creating them. This issue is also mentioned here:
https://devtalk.nvidia.com/default/topic/926824/linux/364-1-2-5-won-t-compile-against-latest-kernel-git-tree-patches-for-4-6-0-rc3-included-/post/4852927/#4852927
suggesting that it is still present, at least, since intel-drm-nightly kernel
4.6. I remember I experienced this bug since late intel-drm-nightly kernel 4.8.

Right now, the only fix to this issue is to set CONFIG_STACK_VALIDATION=n on
the .config file before building the kernel. This solution is also mentioned
here:
https://devtalk.nvidia.com/default/topic/926824/linux/364-1-2-5-won-t-compile-against-latest-kernel-git-tree-patches-for-4-6-0-rc3-included-/post/4854471/#4854471

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170104/bc724271/attachment.html>