mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: NeilBrown <neilb@ownmail.net>
To: Miklos Szeredi <miklos@szeredi.hu>,
	Amir Goldstein <amir73il@gmail.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>,
	"Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-unionfs@vger.kernel.org
Subject: [PATCH 0/3] Fixes for dentry lockdep tracking on stacking filesystems
Date: Sat,  3 Oct 2026 08:35:41 +1000	[thread overview]
Message-ID: <20261002223746.3248726-1-neilb@ownmail.net> (raw)

The recent addition of lockdep tracking for in-lookup dentries didn't
take into account the needs of stacking filesystems.  For this we need
different lock keys for different filesystems in the stack.

Thanks,
NeilBrown


 [PATCH 1/3] VFS: per-fs-type lockdep key for dentry in-lookup locking
 [PATCH 2/3] VFS: rename lookup_map to dep_map
 [PATCH 3/3] ovl: provide private lockdep class for dentry->dep_map

             reply	other threads:[~2026-10-02 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 22:35 NeilBrown [this message]
2026-10-02 22:35 ` [PATCH 1/3] VFS: per-fs-type lockdep key for dentry in-lookup locking NeilBrown
2026-10-02 22:35 ` [PATCH 2/3] VFS: rename lookup_map to dep_map NeilBrown
2026-10-02 22:35 ` [PATCH 3/3] ovl: provide private lockdep class for dentry->dep_map NeilBrown
2026-10-03 12:52   ` Amir Goldstein
2026-10-16  5:47   ` Borah, Chaitanya Kumar
2026-10-16  6:57 ` [PATCH 0/3] Fixes for dentry lockdep tracking on stacking filesystems Amir Goldstein
2026-10-16  8:08 ` Christian Brauner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261002223746.3248726-1-neilb@ownmail.net \
    --to=neilb@ownmail.net \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neil@brown.name \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®