[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64f6bd19-7906-4138-ae1b-a5a443ed140d@sirena.org.uk>
Date: Tue, 13 Jan 2026 17:51:34 +0000
From: Mark Brown <broonie@...nel.org>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: linux-fsdevel@...r.kernel.org, torvalds@...ux-foundation.org,
brauner@...nel.org, jack@...e.cz, mjguzik@...il.com,
paul@...l-moore.com, axboe@...nel.dk, audit@...r.kernel.org,
io-uring@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 15/59] struct filename: saner handling of long names
On Tue, Jan 13, 2026 at 03:39:53PM +0000, Al Viro wrote:
> On Tue, Jan 13, 2026 at 03:31:14PM +0000, Mark Brown wrote:
> > I'm seeing a regression in -next in the execveat kselftest which bisects
> > to 2a0db5f7653b ("struct filename: saner handling of long names"). The
> > test triggers two new failures with very long filenames for tests that
> > previously succeeded:
> Could you check if replacing (in include/linux/fs.h)
> #define EMBEDDED_NAME_MAX 192 - sizeof(struct __filename_head)
> with
> #define EMBEDDED_NAME_MAX (192 - sizeof(struct __filename_head))
> is sufficient for fixing that reproducer?
Yes, that fixes both testcases - thanks!
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists