From: Christoph Hellwig <hch@infradead.org>
To: Celeste <celeste@collar.sh>
Cc: Andrey Albershteyn <aalbersh@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, Carlos Maiolino <cem@kernel.org>
Subject: Re: [PATCH] xfsdump: avoid false-positive __strcpy_chk abort on long dirent names
Date: Fri, 3 Jul 2026 06:03:26 -0700 [thread overview]
Message-ID: <akezHvFoqtKWN0f4@infradead.org> (raw)
In-Reply-To: <DJOCNHYIYK0G.17Q5FWMGKKXMC@collar.sh>
On Thu, Jul 02, 2026 at 12:58:14PM -0700, Celeste wrote:
> should we then assume that this is fine to merge?
I still don't think that just papering over the misuse of the same type
for on-disk and in-memory uses with different characteristics is a good
idea.
next prev parent reply other threads:[~2026-07-03 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 22:23 [PATCH] xfsdump: avoid false-positive __strcpy_chk abort on long dirent names vmfunc
2026-06-25 22:57 ` Darrick J. Wong
2026-06-26 0:28 ` vmfunc
2026-06-26 8:09 ` Christoph Hellwig
2026-06-26 8:11 ` Andrey Albershteyn
2026-07-02 19:58 ` Celeste
2026-07-03 13:03 ` Christoph Hellwig [this message]
2026-07-03 15:49 ` 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=akezHvFoqtKWN0f4@infradead.org \
--to=hch@infradead.org \
--cc=aalbersh@kernel.org \
--cc=celeste@collar.sh \
--cc=cem@kernel.org \
--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