On Wed, Dec 7, 2016 at 1:29 PM, Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx> wrote: > On 12/02/2016 08:03 PM, gregkh@xxxxxxxxxxxxxxxxxxx wrote: >> The patch below was submitted to be applied to the 4.8-stable tree. >> >> I fail to see how this patch meets the stable kernel rules as found at >> Documentation/stable_kernel_rules.txt. >> >> I could be totally wrong, and if so, please respond to >> <stable@xxxxxxxxxxxxxxx> and let me know why this patch should be >> applied. Otherwise, it is now dropped from my patch queues, never to be >> seen again. >> > > Yes, it was seriously submitted to stable. The reason for this is that gcc7 enables > use-after-scope option by default (-fsanitze=kernel-address enables -fsanitize-address-use-after-scope). > With this options gcc7 emits calls to __asan_[un]poison_stack_memory(), > but they are not present in older kernels. So compiling with gcc7 without this patch would cause link errors. > > But I've got better idea. gcc7 isn't released yet, so we can fix this on gcc7 site simply by changing > default to -fNO-sanitize-address-use-after-scope for -fsanitize=kernel-address > > This should be trivial. Dmitry, can you do that? Or we can file a bug and someone else will fix that. Mailed a patch for gcc: https://groups.google.com/forum/#!topic/kasan-dev/D12SNoIUJKI Is it what you mean? Andrey, do you mind mailing a patch for kernel to enable -fsanitize-address-use-after-scope on tip kernels? -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html