Zach Brown 6770a31683 scoutfs: consistently trim srch entry range ...

We have to limit the number of srch entries that we'll track while
performing a search for all the inodes that contain xattrs that match
the search hash value.

As we hit the limit on the number of entries to track we have to drop
entries.  As we drop entries we can't return any inodes for entries
past the dropped entries.  We were updating the end point of the search
as we dropped entries past the tracked set, but we weren't updating the
search end point if we dropped the last currently tracked entry.

And we were setting the end point to the dropped entry, not to the entry
before it.  This could lead us to spuriously returning deleted entries
if we drop the creation entry and then allow tracking its deletion
later.

This fixes both those problems.  We now properly set the end point to
just before the dropped entry for all entries that we drop.

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

2020-12-03 09:58:35 -08:00

kmod

scoutfs: consistently trim srch entry range

2020-12-03 09:58:35 -08:00

Description

No description provided

7.1 MiB

Languages

C 87.1%

Shell 9.2%

Roff 2.5%

TeX 0.9%

Makefile 0.3%