[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170905143125.GD7936@nanopsycho>
Date: Tue, 5 Sep 2017 16:31:25 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kubakici@...pl>
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
Tue, Sep 05, 2017 at 04:25:51PM CEST, kubakici@...pl wrote:
>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
Will try. Thanks!
Powered by blists - more mailing lists