linux-kernel - Re: [RFC] DEPT(DEPendency Tracker) with DLM(Distributed Lock Manager)

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: <20250522052806.GB42746@system.software.com>
Date: Thu, 22 May 2025 14:28:06 +0900
From: Byungchul Park <byungchul@...com>
To: aahringo@...hat.com
Cc: kernel_team@...ynix.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC] DEPT(DEPendency Tracker) with DLM(Distributed Lock Manager)

On Thu, May 22, 2025 at 02:24:53PM +0900, Byungchul Park wrote:
> Hi Alexander,
> 
> We briefly talked about dept with DLM in an external channel.  However,
> it'd be great to discuss what to aim and how to make it in more detail,
> in this mailing list.
> 
> It's worth noting that dept doesn't track dependencies beyond different
> contexts to avoid adding false dependencies by any chance, which means
> though dept checks the dependency sanity *globally*, when it comes to
> creating dependencies, it happens only within e.g. each single system
> call context, each single irq context, each worker context, and so on,
> with its unique context id assigned to each independent context.
> 
> In order for dept to work on DLM, we need a way to assign a unique
> context id to each interesting context in DLM's point of view, and let
> dept know the id.  Once making it done, I think dept can work on DLM
> perfectly.

Plus, we need a way to share the global dependency graph used by dept
between nodes too.

	Byungchul
> 
> Thoughts or any concern?
> 
> 	Byungchul