From: Alyssa Ross <hi@alyssa.is>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] stdio: fix vfscanf with matches longer than INT_MAX (bug 27650)
Date: Sun, 9 May 2021 16:32:18 +0000 [thread overview]
Message-ID: <20210509163218.gtovtfb2jpzode36@eve.qyliss.net> (raw)
In-Reply-To: <87mttc6vpz.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
On Mon, May 03, 2021 at 10:57:12AM +0200, Florian Weimer wrote:
> * Alyssa Ross:
>
> > Patterns like %*[ can safely be used to match a great many characters,
> > and it's quite realisitic to use them for more than INT_MAX characters
> > from an IO stream.
> >
> > With the previous approach, after INT_MAX characters (v)fscanf would
> > return successfully, indicating an end to the match, even though there
> > wasn't one.
>
> I've pushed to this commit, thanks.
>
> We can integrate the test once your copyright assignment is on file.
My copyright assignment should be sorted now (as of May 6).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-05-09 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 14:01 Alyssa Ross
2021-03-25 17:25 ` Florian Weimer
2021-03-25 20:28 ` Alyssa Ross
2021-03-25 21:24 ` Florian Weimer
2021-03-26 12:00 ` Alyssa Ross
2021-03-26 12:17 ` Florian Weimer
2021-03-29 12:01 ` Alyssa Ross
2021-03-29 13:34 ` Florian Weimer
2021-03-29 18:06 ` [PATCH 2/2] stdio: add test for scanf " Alyssa Ross
2021-05-09 21:56 ` Alyssa Ross
2021-05-03 8:57 ` [PATCH] stdio: fix vfscanf with " Florian Weimer
2021-05-09 16:32 ` Alyssa Ross [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=20210509163218.gtovtfb2jpzode36@eve.qyliss.net \
--to=hi@alyssa.is \
--cc=fweimer@redhat.com \
--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).