linux-kernel - Re: [PATCH RT v2] kernel/res_counter.c: Change lock of struct res_counter to raw_spinlock

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]

Date:	Fri, 20 Feb 2015 13:53:24 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
CC:	Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@...com>,
	Thavatchai Makphaibulchoke <tmac@...com>,
	<rostedt@...dmis.org>, <linux-kernel@...r.kernel.org>,
	<mingo@...hat.com>, <tglx@...utronix.de>,
	<linux-rt-users@...r.kernel.org>
Subject: Re: [PATCH RT v2] kernel/res_counter.c: Change lock of struct res_counter
 to raw_spinlock_t

On 2015-02-18 06:05 AM, Sebastian Andrzej Siewior wrote:
> * Paul Gortmaker | 2015-02-13 16:30:17 [-0500]:
>
> there is the thread "[v3.10-rt / v3.12-rt] scheduling while atomic in
> cgroup code" where I applied Mike's patch. This should fix the problem
> reported and be part of the next release.
> Could please double check (either by grabing the patch or waiting for
> the next release).

I've applied Mike's patch from here:

     https://lkml.org/lkml/2014/6/21/11

and tested it on the old dell core2 that reliably showed the splat
at boot, and it is now gone.  This is on vanilla 3.14-rt plus isci
fix + simpleworkqueue + aio-swq fix (all pending for 3.18-rt next).

I also tested it on the 20 core canoe pass where the rawlock
conversion patch from Thavatchai caused strange and unpredictable 
failure modes and that box seems fine with this smaller footprint 
cpulight change.

Paul.
--

>
> Sebastian
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/