From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Andrey Albershteyn <aalbersh@redhat.com>,
xfs <linux-xfs@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] xfs_logprint: fix pointer bug
Date: Tue, 9 Dec 2025 21:25:51 -0800 [thread overview]
Message-ID: <aTkEXwp2zbbAI_jI@infradead.org> (raw)
In-Reply-To: <20251209205738.GY89472@frogsfrogsfrogs>
On Tue, Dec 09, 2025 at 12:57:38PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> generic/055 captures a crash in xfs_logprint due to an incorrect
> refactoring trying to increment a pointer-to-pointer whereas before it
> incremented a pointer.
Oops, sorry. This somehow did not show up in xfstests for me, where
did you run into it?
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-12-10 5:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 20:57 [PATCH] xfs_logprint: fix pointer bug Darrick J. Wong
2025-12-10 5:25 ` Christoph Hellwig [this message]
2025-12-10 6:26 ` Darrick J. Wong
2025-12-10 6:28 ` Christoph Hellwig
2025-12-10 11:10 ` Andrey Albershteyn
2025-12-10 15:44 ` 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=aTkEXwp2zbbAI_jI@infradead.org \
--to=hch@infradead.org \
--cc=aalbersh@redhat.com \
--cc=djwong@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