-a

(assert) Shows information about which lock is supposed to protect each variable, as specified by the assert mutex|rwlock protects subcommand. The information is shown as follows assert=lock

If the assertion is violated, then after analysis this will be preceded by an asterisk, such as *assert=<lock>.

-h

(held) Shows information about which locks were consistently held when the variable was accessed. This information is shown after the analyze subcommand has been run. If the variable was never accessed, this information is not shown. When it is shown, it looks like this:

held={ <lock> ... }

If no locks were consistently held and the variable was written, this is preceded by an asterisk, such as *held={ }. Unlike funcs, the vars subcommand lists a lock as protecting a variable even if the lock was not actually held, but was simply covered by another lock. (See assert rwlock covers in the description of "assert".)

-i

(ignored) causes even ignored variables to be listed.

-l

(long) Equivalent to -aho.

-o

(other) Where applicable, shows information about each variable

=cond_var

Indicates that this variable is used as a condition variable. 

=ignored

Indicates that LockLint has been told to ignore the variable explicitly via an ignore subcommand.

=read-only

Means that LockLint has been told (by assert read only) that the variable is read-only, and will complain if it is written. If it is written, then after analysis this will be followed by an asterisk, such as =read-only* for example.

=readable

Indicates that LockLint has been told by a declare readable subcommand that the variable may be safely read without holding a lock.

=unwritten

May appear after analysis, meaning that while the variable was not declared read-only, it was never written.