1. don't duplicate opts[0].name in the successful output;
2. fix the bug with printing None state, just reuse the OptCheck.result.

Detect STRICT_DEVMEM and IO_STRICT_DEVMEM as not being needed whenever
DEVMEM is not set.

Conflicts resolved by @a13xp0p0v

The OR class implementation supports combining Opt's logically
with an or-operator. If any of the Opt's provided to the OR class
returns True, the check is considered OK.

Fixes #1

Conflicts resolved by @a13xp0p0v

config check is NOT PASSED: 44 errors

config check is NOT PASSED: 33 errors

As requested by a13xp0p0v.

config check is NOT PASSED: 49 errors

config check is NOT PASSED: 49 errors

Linux historical interest is not secure ;)

Conflicts resolved by @a13xp0p0v

Conflicts resolved by @a13xp0p0v:

Also print the value of the unknown option

That will change the check result
  FAIL: "not found"
onto initial
  FAIL: not found

This improves the opt storage using a kconfig key based dict to
avoid looping through all opts to get a certain entry by allowing
key based lookups.

Carefully extracted from their last public patch

STRICT_DEVMEM and IO_STRICT_DEVMEM, SECCOMP and SECCOMP_FILTER
are not self protection features. They cut attack surface.

I'm also not sure about SYN_COOKIES. Mark it with a comment.