linux-kernel - Re: [PATCH -tip 0/2] fix lock inversion in lockless sys

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

Date:	Sun, 14 Sep 2014 11:22:00 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	riel@...hat.com
Cc:	linux-kernel@...r.kernel.org, mingo@...nel.org, prarit@...hat.com,
	oleg@...hat.com, sgruszka@...hat.com
Subject: Re: [PATCH -tip 0/2] fix lock inversion in lockless sys_times()

On Fri, Sep 12, 2014 at 09:12:13AM -0400, riel@...hat.com wrote:
> The sig->stats_lock nests inside the tasklist_lock and the
> sighand->siglock in __exit_signal and wait_task_zombie.
> 
> However, both of those locks can be taken from irq context,
> which means we need to use the interrupt safe variant of
> read_seqbegin_or_lock. This blocks interrupts when the "lock"
> branch is taken (seq is odd), preventing the lock inversion.
> 
> On the first (lockless) pass through the loop, irqs are not
> blocked.
> 
> This fixes the lockdep complaints that Stanislaw reported.
> 

Thanks Rik
--
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/