Yes - LONG_MAX is essentially a "no limit" value as no
container will ever have such many files :)
I'm afraid no. We have to atomically check for limit and alter
one of usage or failcnt depending on the checking result. Making
this with atomic_xxx ops will require at least two ops.
If we'll remove failcnt this would look like
which is also not that good.
Moreover - in RSS accounting patches I perform page list
manipulations under this lock, so this also saves one atomic op.
Nope - when you have a non-static function without users in a
file no compiler warning produced.