CyberDem0n / bg_mon

88%

master: 89%

LAST BUILD ON BRANCH bugfix/buffer-overflow

branch: bugfix/buffer-overflow

CHANGE BRANCH

x

Reset

• bugfix/buffer-overflow
• HEAD
• bugfix/json-escape
• feature/aggregate
• feature/aggregate2
• feature/cgroup
• feature/extended-stats
• feature/lock-memory
• feature/memory-failcnt
• feature/net-and-extended-disk-stats
• feature/pg11
• feature/postgres-13
• feature/refactoring
• feature/safety
• feature/smart-sighup
• feature/start-with-postmaster
• master

Build # 133

Build Type

Pull #20

travis-ci

Committed by web-flow

Commit Message

Fix buffer overflow in get_pg_locks

Every item returned by GetLockStatusData contains information about lock
held mode (ExclusiveLock, AccessShareLock, RowExclusiveLock and so on).
pg_locks view reports all modes for the same object and pg_lock_status()
was copied without full understanding how it supposed to work, what
cause buffer overflow. In fact we are not interested on all modes, but
only about lock status. Taking into account that the given record can
represent granted lock on a given object and at the same time it could
be waiting for a more strict lock, we need to extend array size by 2.

Pull Request Pull Request #20: Fix buffer overflow in get_pg_locks

Run Details

16 of 16 new or added lines in 2 files covered. (100.0%)

1084 of 1233 relevant lines covered (87.92%)

2768.05 hits per line