diff options
author | dim <dim@FreeBSD.org> | 2016-08-09 18:49:19 +0000 |
---|---|---|
committer | dim <dim@FreeBSD.org> | 2016-08-09 18:49:19 +0000 |
commit | 0f996b20a4acb478a13ddb746bc9ee1b321b9bb5 (patch) | |
tree | 0d09f1366e7758063b740dea94e1b84211019e53 /sys/fs/tmpfs/tmpfs_subr.c | |
parent | bf3693f48b1a845cbd0c49bc32044d459a3986f5 (diff) | |
download | FreeBSD-src-0f996b20a4acb478a13ddb746bc9ee1b321b9bb5.zip FreeBSD-src-0f996b20a4acb478a13ddb746bc9ee1b321b9bb5.tar.gz |
MFC r270132 (by gabor):
- Do not look for more matching lines if -L is specified
Submitted by: eadler (based on)
MFC r296799 (by ian):
Fix a bug in bsdgrep that caused the program to hang in a tight loop for
some combinations of command line options and search patterns. The code was
examining regexec flags looking for a regcomp flag value. The fix is to
look in the struct field where the decoded regcomp flag was stored when the
regex was compiled.
With this fix, it's possible to build WITHOUT_GNU_GREP_COMPAT and
WITH_BSDGREP and have a usable GPL-free grep (which of course lacks gnugrep
extensions). It now passes the kyua tests except for one test that requires
the -z/--null-data gnu extension, and one test involving outputting context
lines across multiple files which appears to sometimes output an extra
delimiter line ("--") between matches (a rather obscure failure of a rather
obscure feature, so bsdgrep should be generally usable now).
MFC r303676:
Fix a segfault in bsdgrep when parsing the invalid extended regexps "?"
or "+" (these are invalid, because there is no preceding operand).
When bsdgrep attempts to emulate GNU grep in discarding and ignoring the
invalid ? or + operators, some later logic in tre_compile_fast() goes
beyond the end of the buffer, leading to a crash.
Fix this by bailing out, and reporting a bad pattern instead.
Reported by: Steve Kargl
Diffstat (limited to 'sys/fs/tmpfs/tmpfs_subr.c')
0 files changed, 0 insertions, 0 deletions