From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: cem@kernel.org, hch@lst.de, stable@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/6] xfs: don't modify file attributes or poke fsnotify for dry runs
Date: Wed, 2 Sep 2026 09:13:23 +0200 [thread overview]
Message-ID: <20260902071323.GA25939@lst.de> (raw)
In-Reply-To: <178832749528.3507209.11787129781318331688.stgit@frogsfrogsfrogs>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-09-02 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 5:41 [PATCHSET v2 2/5] xfs: LLM-inspired bug fixes, part 6 Darrick J. Wong
2026-09-02 5:43 ` [PATCH 1/6] xfs: fix xfs_rtrmapbt_mem_cursor for non-rmap filesystems Darrick J. Wong
2026-09-02 5:43 ` [PATCH 2/6] xfs: preserve owner on in-memory btree creation Darrick J. Wong
2026-09-02 5:44 ` [PATCH 3/6] xfs: don't leak new_bp if xfs_btree_bload_drop_buf fails Darrick J. Wong
2026-09-02 5:44 ` [PATCH 4/6] xfs: actually recover intended file sizes in xfs_xmi_item_recover_intent Darrick J. Wong
2026-09-02 5:44 ` [PATCH 5/6] xfs: don't modify file attributes or poke fsnotify for dry runs Darrick J. Wong
2026-09-02 7:13 ` Christoph Hellwig [this message]
2026-09-02 5:44 ` [PATCH 6/6] xfs: fix bnobt repair space reservation disposal failure Darrick J. Wong
2026-09-07 6:30 ` [PATCHSET v2 2/5] xfs: LLM-inspired bug fixes, part 6 Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2026-08-13 5:24 [PATCHSET 2/2] " Darrick J. Wong
2026-08-13 5:26 ` [PATCH 5/6] xfs: don't modify file attributes or poke fsnotify for dry runs Darrick J. Wong
2026-08-19 6:24 ` Christoph Hellwig
2026-08-19 23:24 ` 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=20260902071323.GA25939@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@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 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.