All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>, Daire Byrne <daire@dneg.com>,
	Andreas Dilger <adilger.kernel@dilger.ca>
Subject: Re: [PATCH/RFC] VFS: support parallel updates in the one directory.
Date: Tue, 22 Feb 2022 16:11:44 -0500	[thread overview]
Message-ID: <20220222211144.GA9541@fieldses.org> (raw)
In-Reply-To: <20220222190751.GA7766@fieldses.org>

On Tue, Feb 22, 2022 at 02:07:51PM -0500, bfields wrote:
> For what it's worth, I applied this to recent upstream (038101e6b2cd)
> and fed it through my usual scripts--tests all passed, but I did see
> this lockdep warning.
> 
> I'm not actually sure what was running at the time--probably just cthon.

Yeah, reproduceable just by running "cthon -b -f" over an NFS mount.

--b.

  reply	other threads:[~2022-02-22 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  2:24 [PATCH/RFC] VFS: support parallel updates in the one directory NeilBrown
2022-02-22 19:07 ` J. Bruce Fields
2022-02-22 21:11   ` J. Bruce Fields [this message]
2022-02-24  5:08   ` NeilBrown
2022-02-24 21:23     ` J. Bruce Fields
2022-02-22 22:45 ` Dave Chinner
2022-02-24  4:43   ` Darrick J. Wong
2022-02-24  5:56     ` NeilBrown
2022-02-24 16:31       ` Andreas Dilger
2022-02-24 23:38         ` Darrick J. Wong
2022-02-25 23:16           ` Dave Chinner
2022-02-28  0:55           ` NeilBrown
2022-03-10 11:10             ` Daire Byrne
2022-02-25 23:07     ` Dave Chinner

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=20220222211144.GA9541@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=daire@dneg.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.