audit: Make testing for a valid loginuid explicit.

audit rule additions containing "-F auid!=4294967295" were failing
with EINVAL because of a regression caused by e1760bd.

Apparently some userland audit rule sets want to know if loginuid uid
has been set and are using a test for auid != 4294967295 to determine
that.

In practice that is a horrible way to ask if a value has been set,
because it relies on subtle implementation details and will break
every time the uid implementation in the kernel changes.

So add a clean way to test if the audit loginuid has been set, and
silently convert the old idiom to the cleaner and more comprehensible
new idiom.

Cc: <[email protected]> # 3.7
Reported-By: Richard Guy Briggs <[email protected]>
Signed-off-by: "Eric W. Biederman" <[email protected]>
Tested-by: Richard Guy Briggs <[email protected]>
Signed-off-by: Eric Paris <[email protected]>

0 files changed, 0 insertions, 0 deletions