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:   Mon, 1 Apr 2019 10:14:24 -0300
From:   Marcelo Ricardo Leitner <>
To:     Kevin 'ldir' Darbyshire-Bryant <>
Cc:     "" <>,
        "" <>,
        "" <>,
        "" <>,
        Paul Blakey <>, Oz Shlomo <>
Subject: Re: [RFC net-next 0/1] net: sched: Introduce conntrack action


On Fri, Mar 29, 2019 at 08:45:06PM +0000, Kevin 'ldir' Darbyshire-Bryant wrote:
> Hi Cong,
> OK, so I've renamed conndscp to conntrack and hopefully this are
> flexible enough for future conntrack->skb operations to be added in the
> future.  How does this one fly?

This work sort of clashes with the work that Paul Blakey and I are
doing to integrate conntrack with tc and vice-versa.

Considering that in this patch the action is not RCU-ified, that it is
using a struct as netlink parameter and it is dealing only with the
dscp info, seems it's easier if we/you extend our code to support this
feature as well.  How does that sound to you?

The RFC I had posted is VERY outdated (message-id, please don't use it as
reference.  Not sure if Paul can post a refreshed RFC already.


Powered by blists - more mailing lists