All of lore.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Jakub Wilk <jwilk@jwilk.net>,  linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man3/opendir.3: document that long file names result in ENAMETOOLONG
Date: Tue, 28 Oct 2025 17:29:58 -0700	[thread overview]
Message-ID: <87ms5a5z3t.fsf@gmail.com> (raw)
In-Reply-To: <um3c7pddogzafccx5wtr5pzpyle7ve5xbcl4wrx4sk3yzkrere@euo5ol6ekmqr>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

Alejandro Colomar <alx@kernel.org> writes:

> Hi Collin, Jakub,
>
> On Fri, Oct 17, 2025 at 10:45:53AM +0200, Jakub Wilk wrote:
>> * Collin Funk <collin.funk1@gmail.com>, 2025-10-17 01:18:
>> >    $ mkdir -p `python3 -c 'print("./" + "a/" * 32768)'`
>> >    $ ./a.out `python3 -c 'print("./" + "a/" * 32768)'`
>> >    File name too long
>
> Thanks!  I've applied the patch.
>
>> 
>> Simpler reproducer:
>> 
>> $ ./a.out $(printf '%0999d')
>> File name too long
>
> And also thanks!  I've amended the commit message to use the simpler
> reproducer.

Thanks! That is fine. My example was a longer than needed since I was
testing long path handling in Coreutils and wanted deep directory
entries.

Collin


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2025-10-29  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  8:18 [PATCH] man/man3/opendir.3: document that long file names result in ENAMETOOLONG Collin Funk
2025-10-17  8:45 ` Jakub Wilk
2025-10-28 23:37   ` Alejandro Colomar
2025-10-29  0:29     ` Collin Funk [this message]

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=87ms5a5z3t.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=alx@kernel.org \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@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.