linux-kernel - Re: [GIT PULL] timer fixes

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]

Message-ID: <Yvi5DMkZJlaj2rBx@gmail.com>
Date:   Sun, 14 Aug 2022 10:57:48 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Borislav Petkov <bp@...en8.de>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-kernel@...r.kernel.org,
        Peter Zijlstra <peterz@...radead.org>, x86-ml <x86@...nel.org>
Subject: Re: [GIT PULL] timer fixes


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> I think the issue is that "current->sighand" is always safe (and that 
> "me->sighand" is the same thing), and that sighand has RCU-delayed 
> freeing so that __lock_task_sighand() can safely try to take the lock of 
> another process' sighand.

Yeah - 'me' (== current) here can never go away from under the locking 
context which is 'me' as well.

Thanks,

	Ingo