Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 23 Nov 2020 20:05:27 +0900
From:   Byungchul Park <byungchul.park@lge.com>
To:     torvalds@linux-foundation.org, peterz@infradead.org,
        mingo@redhat.com, will@kernel.org
Cc:     linux-kernel@vger.kernel.org, tglx@linutronix.de,
        rostedt@goodmis.org, joel@joelfernandes.org,
        alexander.levin@microsoft.com, daniel.vetter@ffwll.ch,
        chris@chris-wilson.co.uk, duyuyang@gmail.com,
        johannes.berg@intel.com, tj@kernel.org, tytso@mit.edu,
        willy@infradead.org, david@fromorbit.com, amir73il@gmail.com,
        bfields@fieldses.org, gregkh@linuxfoundation.org,
        kernel-team@lge.com
Subject: [RFC] Dept(Dependency Tracker) Implementation
Message-ID: <20201123110527.GB9464@X58A-UD3R>
References: <20201111050559.GA24438@X58A-UD3R>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201111050559.GA24438@X58A-UD3R>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk

Hi,

This patchset is too nasty to get reviewed in detail for now.

This have:

   1. applying Dept to spinlock/mutex/rwlock/completion
   2. assigning custom keys or disable maps to avoid false positives

This doesn't have yet (but will be done):

   1. proc interfaces e.g. to see dependecies the tool has built,
   2. applying Dept to rw semaphore and the like,
   3. applying Dept to lock_page()/unlock_page(),
   4. assigning custom keys to more places properly,
   5. replace all manual Lockdep annotations,
   (and so on..)

But I decided to share it to let others able to test how it works and
someone who wants to see the detail able to check the code. The most
important thing I'd like to show is what exactly a deadlock detection
tool should do.

Turn on CONFIG_DEPT to test it. Feel free to leave any questions if you
have.

Thanks,
Byungchul