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: <20190507110847.GA2157@nanopsycho>
Date:   Tue, 7 May 2019 13:08:47 +0200
From:   Jiri Pirko <jiri@...nulli.us>
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org,
        oss-drivers@...ronome.com, xiyou.wangcong@...il.com,
        Pieter Jansen van Vuuren 
        <pieter.jansenvanvuuren@...ronome.com>,
        Jiri Pirko <jiri@...lanox.com>
Subject: Re: [PATCH net-next] net/sched: remove block pointer from common
 offload structure

Tue, May 07, 2019 at 02:24:21AM CEST, jakub.kicinski@...ronome.com wrote:
>From: Pieter Jansen van Vuuren <pieter.jansenvanvuuren@...ronome.com>
>
>Based on feedback from Jiri avoid carrying a pointer to the tcf_block
>structure in the tc_cls_common_offload structure. Instead store
>a flag in driver private data which indicates if offloads apply
>to a shared block at block binding time.
>
>Suggested-by: Jiri Pirko <jiri@...lanox.com>
>Signed-off-by: Pieter Jansen van Vuuren <pieter.jansenvanvuuren@...ronome.com>
>Reviewed-by: Jakub Kicinski <jakub.kicinski@...ronome.com>

Acked-by: Jiri Pirko <jiri@...lanox.com>

Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ