Ran
|
Jobs
1
|
Files
89
|
Run time
4s
|
Badge
Embed ▾
README BADGES
|
push
github
Fix predict_next() in parser (again). Reported by Sergey Bronnikov. (cherry picked from commit 309fb42b8) The following Lua snippet triggers out-of-boundary access to a stack: ``` a, b, c = 1, 2, 3 local d for _ in nil do end ``` During the execution of this snippet with LuaJIT instrumented by ASAN, it leads to a heap-based buffer overflow. In function `predict_next()` variable `exprpc` looks forward and expects extra bytecodes on the stack. However, `KPRI` is merged to `KNIL` and there is no new bytecode to add, so `exprpc == fs->bclim`, and it leads to out-of-boundary access. Issue has been fixed by an early return when `pc >= fs->bclim`. Sergey Bronnikov: * added the description and the test for the problem Part of tarantool/tarantool#8825
5330 of 5969 branches covered (0.0%)
Branch coverage included in aggregate %.
20423 of 23288 relevant lines covered (87.7%)
1296925.27 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
95.64 |
-0.05% | src/lj_record.c |
3 |
95.19 |
-0.71% | src/lj_opt_mem.c |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 6036840294.1 | 89 |
88.02 |
GitHub Action Run |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|