From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: libc-alpha@sourceware.org
Cc: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: [PATCH 1/2] fnmatch: allow character class names with 'z'
Date: Tue, 23 May 2023 00:37:31 -0700 [thread overview]
Message-ID: <20230523073732.6956-2-carenas@gmail.com> (raw)
In-Reply-To: <20230523073732.6956-1-carenas@gmail.com>
Since d8aaef00a7 (Update., 1999-04-26), there is code to consider
character class names that include that character as invalid
* posix/fnmatch_loop.c: correct inequality
Copyright-paperwork-exempt: yes
---
posix/fnmatch_loop.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/posix/fnmatch_loop.c b/posix/fnmatch_loop.c
index 8aeec9816f..4be2e20141 100644
--- a/posix/fnmatch_loop.c
+++ b/posix/fnmatch_loop.c
@@ -283,7 +283,7 @@ FCT (const CHAR *pattern, const CHAR *string, const CHAR *string_end,
p += 2;
break;
}
- if (c < L_('a') || c >= L_('z'))
+ if (c < L_('a') || c > L_('z'))
{
/* This cannot possibly be a character class name.
Match it as a normal range. */
--
2.39.2
next prev parent reply other threads:[~2023-05-23 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 7:37 [PATCH 0/2] posix: fix fnmatch() inconsistency BZ#30483 Carlo Marcelo Arenas Belón
2023-05-23 7:37 ` Carlo Marcelo Arenas Belón [this message]
2023-05-23 18:09 ` [PATCH 1/2] fnmatch: allow character class names with 'z' Adhemerval Zanella Netto
2023-05-23 21:55 ` Carlo Arenas
2023-05-26 14:25 ` Adhemerval Zanella Netto
2023-05-23 7:37 ` [PATCH 2/2] posix: correctly detect invalid classes after match in fnmatch() Carlo Marcelo Arenas Belón
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=20230523073732.6956-2-carenas@gmail.com \
--to=carenas@gmail.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).