netdev - Re: [RFC net-next 06/15] devlink: use an explicit structure for dump context

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221215111852.3b2a60ab@kernel.org>
Date:   Thu, 15 Dec 2022 11:18:52 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Jacob Keller <jacob.e.keller@...el.com>
Cc:     <davem@...emloft.net>, <netdev@...r.kernel.org>,
        <edumazet@...gle.com>, <pabeni@...hat.com>, <jiri@...nulli.us>,
        <leon@...nel.org>
Subject: Re: [RFC net-next 06/15] devlink: use an explicit structure for
 dump context

On Thu, 15 Dec 2022 10:50:11 -0800 Jacob Keller wrote:
> And to be clear, the context is not ABI since its not exported outside 
> the kernel. Thus, these changes don't break compatibility with user space.

Yes, indeed.