[lkml]   [2018]   [Feb]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [tip:x86/urgent] x86/dumpstack: Avoid uninitlized variable
On Fri, Feb 2, 2018 at 11:36 PM, tip-bot for Arnd Bergmann
<> wrote:
> Commit-ID: ebfc15019cfa72496c674ffcb0b8ef10790dcddc
> Gitweb:
> Author: Arnd Bergmann <>
> AuthorDate: Fri, 2 Feb 2018 15:56:17 +0100
> Committer: Thomas Gleixner <>
> CommitDate: Fri, 2 Feb 2018 23:33:50 +0100
> x86/dumpstack: Avoid uninitlized variable
> In some configurations, 'partial' does not get initialized, as shown by
> this gcc-8 warning:
> arch/x86/kernel/dumpstack.c: In function 'show_trace_log_lvl':
> arch/x86/kernel/dumpstack.c:156:4: error: 'partial' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> show_regs_if_on_stack(&stack_info, regs, partial);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This initializes it to false, to get the previous behavior in this case.
> Fixes: a9cdbe72c4e8 ("x86/dumpstack: Fix partial register dumps")

I just noticed my annotation got lost when I sent the patch. I originally
meant to ask Josh to double-check whether it should be 'false' or 'true'
here, or if we maybe need a larger change.

Josh, could you take a look? Unfortunately I did not really understand
your original commit, so I don't know what the safe choice is here
in those cases in which 'partial' is uninitialized.


 \ /
  Last update: 2018-02-05 22:21    [W:0.079 / U:0.824 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site