Zach Brown 47f5946c90 scoutfs: fix lock name comparison ...

The lock name comparison had a typo where it didn't compare the second
fields between the two names.  Only inode index items used the second
field.  This bug could cause lock matching when the names don't match
and trigger lock coverage warnings.

While we're in there don't rely so heavily on readers knowing the
relative precedence of subtraction and (magical gcc empty) ternary
operators.

Signed-off-by: Zach Brown <zab@versity.com>

2017-10-09 15:31:29 -07:00

kmod

scoutfs: fix lock name comparison

2017-10-09 15:31:29 -07:00

Description

No description provided

6.5 MiB

Languages

C 86.4%

Shell 10%

Roff 2.5%

TeX 0.8%

Makefile 0.3%