netdev - Re: [PATCHv3 next 0/3] blackhole device to invalidate dst

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

Message-Id: <20190701.193516.551631803622082346.davem@davemloft.net>
Date:   Mon, 01 Jul 2019 19:35:16 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     maheshb@...gle.com
Cc:     netdev@...r.kernel.org, edumazet@...gle.com,
        michael.chan@...adcom.com, dja@...ens.net, mahesh@...dewar.net
Subject: Re: [PATCHv3 next 0/3] blackhole device to invalidate dst

From: Mahesh Bandewar <maheshb@...gle.com>
Date: Mon,  1 Jul 2019 14:38:43 -0700

 ...
> The idea here is to not alter the data-path with additional
> locks or smb()/rmb() barriers to avoid racy assignments but
> to create a new device that has really low MTU that has
> .ndo_start_xmit essentially a kfree_skb(). Make use of this
> device instead of 'lo' when marking the dst dead.
> 
> First patch implements the blackhole device and second
> patch uses it in IPv4 and IPv6 stack while the third patch
> is the self test that ensures the sanity of this device.
 ...

Series applied to net-next, thanks.