linux-kernel - Re: feature detection versus feature selection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160814110403.GC19532@krava>
Date:	Sun, 14 Aug 2016 13:04:03 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	Jiri Olsa <jolsa@...nel.org>, Wang Nan <wangnan0@...wei.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: feature detection versus feature selection

On Fri, Aug 12, 2016 at 01:15:00PM -0300, Arnaldo Carvalho de Melo wrote:
> Hey guys,
> 
> 	Now we have this output when building tools with the feature
> detection mechanisms in tools/build/:
> 
> Auto-detecting system features:
> ...                         dwarf: [ on  ]
> ...            dwarf_getlocations: [ OFF ]
> ...                         glibc: [ on  ]
> ...                          gtk2: [ on  ]
> ...                      libaudit: [ on  ]
> ...                        libbfd: [ on  ]
> ...                        libelf: [ on  ]
> ...                       libnuma: [ on  ]
> ...        numa_num_possible_cpus: [ OFF ]
> ...                       libperl: [ on  ]
> ...                     libpython: [ on  ]
> ...                      libslang: [ on  ]
> ...                     libcrypto: [ on  ]
> ...                     libunwind: [ on  ]
> ...            libdw-dwarf-unwind: [ OFF ]
> ...                          zlib: [ on  ]
> ...                          lzma: [ on  ]
> ...                     get_cpuid: [ on  ]
> ...                           bpf: [ on  ]
> 
> 
> 	What I miss is a way to have another column that would state if
> the user had used, say, NO_LIBELF to disable libelf...
> 
> 	Jiri, is there already some file where we have the list of
> manually disabled features? Or do you have something like that in mind?
> .config files?

my mind is empty ;-)

we could add map for that, or we could just add:

...                        libbfd: [ on  ]
...                        libelf: [ OFF NO_LIBELF ]
...                       libnuma: [ on  ]
...        numa_num_possible_cpus: [ OFF ]

jirka