linux-kernel - Re: [PATCH 0/5] Handling for TAP header level

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 for Android: free password hash cracker in your pocket

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

Date:   Sat, 24 Feb 2018 09:39:14 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Shuah Khan <shuahkh@....samsung.com>
Cc:     shuah@...nel.org, dvhart@...radead.org, tbird20d@...il.com,
        tglx@...utronix.de, mingo@...hat.com, peterz@...radead.org,
        linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 0/5] Handling for TAP header level


* Shuah Khan <shuahkh@....samsung.com> wrote:

> This patch series is a result discussion with Tim Bird about nested TAP header 
> handling. Based on the discussion, I am introducing a environment variable to 
> prevent nested TAP headers. These patches improve the run_tests output and the 
> output from the script generated by emit_tests.

Could you please provider a higher level description about what 'nested TAP header 
handling' is about and what it is good for?

Thanks,

	Ingo