|author||Rich Felker <firstname.lastname@example.org>||2015-03-30 02:13:59 -0400|
|committer||Rich Felker <email@example.com>||2015-03-30 02:13:59 -0400|
fix regcomp handling of backslash followed by high byte
the regex parser handles the (undefined) case of an unexpected byte following a backslash as a literal. however, instead of correctly decoding a character, it was treating the byte value itself as a character. this was not only semantically unjustified, but turned out to be dangerous on archs where plain char is signed: bytes in the range 252-255 alias the internal codes -4 through -1 used for special types of literal nodes in the AST. analogous to commit 39dfd58417ef642307d90306e1c7e50aaec5a35c in mainline. it's unclear whether the same crash that affected mainline is possible in the older regcomp code in 1.0.x, but conceptually the bug is the same.
Diffstat (limited to 'src/dirent')
0 files changed, 0 insertions, 0 deletions