public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: cem@kernel.org, brauner@kernel.org, linux-xfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fserror: fix lockdep complaint when igrabbing inode
Date: Thu, 19 Feb 2026 14:52:14 -0800	[thread overview]
Message-ID: <20260219225214.GT6490@frogsfrogsfrogs> (raw)
In-Reply-To: <aZa0XkylrjTYR5pg@infradead.org>

On Wed, Feb 18, 2026 at 10:57:34PM -0800, Christoph Hellwig wrote:
> Allright, this is basically a dumbed down version of the XFS ioend queuing
> just for errors.  I don't particularly like it, but it's probably good
> enough to fix the regression:

Yeah, let's hope so.  Thanks for hodling your nose. :)

--D

> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 
> 

  reply	other threads:[~2026-02-19 22:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  6:09 [PATCHSET] fs: bug fixes for 7.0 Darrick J. Wong
2026-02-19  6:09 ` [PATCH 1/2] fsnotify: drop unused helper Darrick J. Wong
2026-02-19  6:53   ` Christoph Hellwig
2026-02-19 11:37   ` Jan Kara
2026-02-19  6:09 ` [PATCH 2/2] fserror: fix lockdep complaint when igrabbing inode Darrick J. Wong
2026-02-19  6:15   ` Darrick J. Wong
2026-02-19  8:11     ` Christian Brauner
2026-02-20  0:55       ` Darrick J. Wong
2026-02-19  6:57   ` Christoph Hellwig
2026-02-19 22:52     ` Darrick J. Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-20  1:00 [PATCHSET v2 2/2] fs: bug fixes for 7.0 Darrick J. Wong
2026-02-20  1:02 ` [PATCH 2/2] fserror: fix lockdep complaint when igrabbing inode Darrick J. Wong

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=20260219225214.GT6490@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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