netdev - Re: [oss-drivers] Re: [PATCH net] net: sched: don't use GFP

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]

Date:   Tue, 5 Sep 2017 15:25:51 +0100
From:   Jakub Kicinski <kubakici@...pl>
To:     Jiri Pirko <jiri@...nulli.us>
Cc:     netdev@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [oss-drivers] Re: [PATCH net] net: sched: don't use GFP_KERNEL
 under spin lock

On Tue, 5 Sep 2017 14:52:21 +0200, Jiri Pirko wrote:
> Tue, Sep 05, 2017 at 12:59:48PM CEST, kubakici@...pl wrote:
> >Jiri, FWIW I also just noticed these, but they seem related to the
> >earlier TC chain work?  
> 
> What do you do to trigger this?

Sorry, I wasted a bit of time there because kmemleak takes surprisingly
long to notice the memory leak...  In the end this is sufficient:

 modprobe nfp
 ifconfig p4p1 10.8.1.1/24 up
 tc qdisc add dev p4p1 handle ffff: ingress
 tc filter add dev p4p1 parent ffff: protocol 802.1Q flower vlan_id 600 \
     action mirred egress redirect dev p4p1
 tc filter del dev p4p1 parent ffff:
 rmmod nfp