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]
Message-Id: <20181211.111420.9962444018507543.davem@davemloft.net>
Date:   Tue, 11 Dec 2018 11:14:20 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     fw@...len.de
Cc:     pablo@...filter.org, netdev@...r.kernel.org, f.fainelli@...il.com,
        jiri@...lanox.com, mkubecek@...e.cz
Subject: Re: [net-next,v5,00/12] add flow_rule infrastructure

From: Florian Westphal <fw@...len.de>
Date: Tue, 11 Dec 2018 16:35:19 +0100

> Pablo Neira Ayuso <pablo@...filter.org> wrote:
> 
> [ trimming CCs ]
> 
>> This is another iteration of the in-kernel intermediate representation
>> (IR) that allows to express ACL hardware offloads using one unified
>> representation from the driver side for the ethtool and the tc
>> frontends [1] [2] [3].
> 
> [..]
> 
> This is marked 'rejected' in patchwork, what happened?

Pablo is not being honest about his true intentions and long term
goals with this series.  Or also brought up fundamental objections
against previous versions of this series which were not sufficiently
addressed by Pablo.

My personal concern has been brought up several times.

I am not going to restate the same thing over and over, and he hasn't
fixed up his introductory posting in response to my concerns in any
meaningful and full way.

Therefore, if I feel like my and Or's feedback will keep being
ignored, I will keep rejecting these changes.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ