linux-kernel - Re: [PATCH 6/6] Makes procs file writable to move all threads by tgid at once

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: <6599ad830908050911t6f23f810i65fe8fe17f3ee698@mail.gmail.com>
Date:	Wed, 5 Aug 2009 09:11:40 -0700
From:	Paul Menage <menage@...gle.com>
To:	Paul Menage <menage@...gle.com>, Benjamin Blum <bblum@...gle.com>,
	containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH 6/6] Makes procs file writable to move all threads by tgid 
	at once

On Wed, Aug 5, 2009 at 3:20 AM, Louis Rilling<Louis.Rilling@...labs.com> wrote:
>
> The downside of this is teaching lockdep about this recursive locking. Not that
> simple actually...

Don't we just give each thread's lock its own lock class? That's what
we did for the cgroup hierarchy_mutex.

> so that such cases are currently handled using a higher-level
> lock that prevents races in locking the whole chain (there was one such example
> for locking all vmas with KVM). IIUC, the intent here is to avoid such
> higher-level lock.

cgroup_mutex already fulfills the role of the higher-level lock.

Paul
--
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/