From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH v5] io: Fix ftw internal realloc buffer (BZ #28126)
Date: Mon, 13 Sep 2021 18:45:53 +0530 [thread overview]
Message-ID: <ad3a9c6f-f85f-b561-77b4-c1295e96acb1@gotplt.org> (raw)
In-Reply-To: <20210907123352.132575-1-adhemerval.zanella@linaro.org>
On 9/7/21 6:03 PM, Adhemerval Zanella via Libc-alpha wrote:
> The 106ff08526d3ca did not take in consideration the buffer might be
> reallocated if the total path is larger than PATH_MAX. The realloc
> uses 'dirbuf', where 'dirstreams' is the allocated buffer.
>
> Checked on x86_64-linux-gnu.
The new test seems to be failing on i686:
https://www.delorie.com/trybots/32bit/2760/io-tst-ftw-bz28126.out
Siddhesh
prev parent reply other threads:[~2021-09-13 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 12:33 [PATCH v5] io: Fix ftw internal realloc buffer (BZ #28126) Adhemerval Zanella via Libc-alpha
2021-09-13 13:15 ` Siddhesh Poyarekar [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad3a9c6f-f85f-b561-77b4-c1295e96acb1@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).