linux-kernel - Re: [v4.14-rt][report] arm: just another rcu_note_context

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1399f473-b743-8030-bf3e-9835596522e7@ti.com>
Date:   Fri, 16 Feb 2018 12:26:36 -0600
From:   Grygorii Strashko <grygorii.strashko@...com>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
CC:     Steven Rostedt <rostedt@...dmis.org>,
        linux-rt-users <linux-rt-users@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [v4.14-rt][report] arm: just another rcu_note_context_switch



On 02/16/2018 05:30 AM, Sebastian Andrzej Siewior wrote:
> On 2018-02-14 16:12:42 [-0600], Grygorii Strashko wrote:
>> Hi All,
> Hi,
> 
>> I can see below warning during boot on few TI boards am437x-idk, am335x-evm, am335x-ice
>> All of them are non-SMP
> 
> I somehow missed the !SMP kernel… What about this:
> 
> Subject: [PATCH] RCU: skip the "schedule() in RCU section" warning on UP, too
> 
> In "RCU: we need to skip that warning but only on sleeping locks" we
> skipped a warning on SMP systems in case we schedule out in a RCU
> section while attempt to obtain a sleeping lock. This is also required
> on UP systems.
> In order to do so, I introduce a tiny version of migrate_disable() +
> _enable() which only update the counters which we then can check against
> on RT && !SMP.
> 
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> ---

Thanks. I do not see errors any more.
Tested-by: Grygorii Strashko <grygorii.strashko@...com>



-- 
regards,
-grygorii