lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1544176449.1251.6.camel@mtksdccf07>
Date:   Fri, 7 Dec 2018 18:00:20 +0800
From:   Kathleen Chang <yt.chang@...iatek.com>
To:     <mingo@...hat.com>
CC:     <wsd_upstream@...iatek.com>
Subject: sched: panic() in schedule_bug

hi, 

[kernel-4.9, kernel-4.14] 


When preemption disable in schedule(), 
Current linux design will panic when panic_on_warn=1 

However, 
   default setting, panic_on_warn=0,  and 
   if panic_on_warn=1  , and call panic() after printing out WARN()
location.  It affects too much cases.  

Could panic directly without checking panic_on_warn? 
This is obviously incorrect behavior, and should be panic to prevent
misbehavior.  


        if (panic_on_warn)
                panic("scheduling while atomic\n");


thanks!  


=============================
kernel/sched/core.c

schedule_debug =>  when in atomic preempt off   => __schedule_bug 

====



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ