netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kubakici@wp.pl>
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net] net: sched: don't use GFP_KERNEL under spin lock
Date: Tue, 5 Sep 2017 14:52:21 +0200	[thread overview]
Message-ID: <20170905125221.GA7936@nanopsycho> (raw)
In-Reply-To: <20170905115948.2fd38785@cakuba.netronome.com>

Tue, Sep 05, 2017 at 12:59:48PM CEST, kubakici@wp.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?

>
>unreferenced object 0xffff8807466f70c8 (size 64):
>  comm "tc", pid 1812, jiffies 4294932641 (age 1537.192s)
>  hex dump (first 32 bytes):
>    00 00 00 00 00 00 00 00 a0 83 e1 31 07 88 ff ff  ...........1....
>    d8 70 6f 46 07 88 ff ff d8 70 6f 46 07 88 ff ff  .poF.....poF....
>  backtrace:
>    [<ffffffffaa6b0118>] kmemleak_alloc+0x28/0x50
>    [<ffffffffa89a89b6>] kmem_cache_alloc_trace+0x1e6/0x550
>    [<ffffffffaa102827>] tcf_chain_create+0x97/0x460
>    [<ffffffffaa102f67>] tcf_block_get+0x127/0x230
>    [<ffffffffc03e8546>] ingress_init+0x76/0x110 [sch_ingress]
>    [<ffffffffaa0fbb1c>] qdisc_create+0x2ec/0x1100
>    [<ffffffffaa0fce1a>] tc_modify_qdisc+0x4ea/0x1ae0
>    [<ffffffffaa0355dc>] rtnetlink_rcv_msg+0xa3c/0x1400
>    [<ffffffffaa12e3cb>] netlink_rcv_skb+0x22b/0x4e0
>    [<ffffffffaa024b55>] rtnetlink_rcv+0x15/0x20
>    [<ffffffffaa12bddd>] netlink_unicast+0x47d/0x710
>    [<ffffffffaa12caef>] netlink_sendmsg+0xa7f/0x1140
>    [<ffffffffa9f15c52>] sock_sendmsg+0xe2/0x170
>    [<ffffffffa9f188bd>] ___sys_sendmsg+0x72d/0xcc0
>    [<ffffffffa9f1bfa2>] __sys_sendmsg+0xe2/0x260
>    [<ffffffffa9f1c132>] SyS_sendmsg+0x12/0x20
>unreferenced object 0xffff88074db6c008 (size 64):
>  comm "tc", pid 2097, jiffies 4294953636 (age 1453.212s)
>  hex dump (first 32 bytes):
>    00 00 00 00 00 00 00 00 60 a6 d1 31 07 88 ff ff  ........`..1....
>    18 c0 b6 4d 07 88 ff ff 18 c0 b6 4d 07 88 ff ff  ...M.......M....
>  backtrace:
>    [<ffffffffaa6b0118>] kmemleak_alloc+0x28/0x50
>    [<ffffffffa89a89b6>] kmem_cache_alloc_trace+0x1e6/0x550
>    [<ffffffffaa102827>] tcf_chain_create+0x97/0x460
>    [<ffffffffaa102f67>] tcf_block_get+0x127/0x230
>    [<ffffffffc03e8546>] ingress_init+0x76/0x110 [sch_ingress]
>    [<ffffffffaa0fbb1c>] qdisc_create+0x2ec/0x1100
>    [<ffffffffaa0fce1a>] tc_modify_qdisc+0x4ea/0x1ae0
>    [<ffffffffaa0355dc>] rtnetlink_rcv_msg+0xa3c/0x1400
>    [<ffffffffaa12e3cb>] netlink_rcv_skb+0x22b/0x4e0
>    [<ffffffffaa024b55>] rtnetlink_rcv+0x15/0x20
>    [<ffffffffaa12bddd>] netlink_unicast+0x47d/0x710
>    [<ffffffffaa12caef>] netlink_sendmsg+0xa7f/0x1140
>    [<ffffffffa9f15c52>] sock_sendmsg+0xe2/0x170
>    [<ffffffffa9f188bd>] ___sys_sendmsg+0x72d/0xcc0
>    [<ffffffffa9f1bfa2>] __sys_sendmsg+0xe2/0x260
>    [<ffffffffa9f1c132>] SyS_sendmsg+0x12/0x20
>unreferenced object 0xffff880749f82a48 (size 64):
>  comm "tc", pid 2381, jiffies 4294972986 (age 1375.812s)
>  hex dump (first 32 bytes):
>    00 00 00 00 00 00 00 00 c0 b7 31 31 07 88 ff ff  ..........11....
>    58 2a f8 49 07 88 ff ff 58 2a f8 49 07 88 ff ff  X*.I....X*.I....
>  backtrace:
>    [<ffffffffaa6b0118>] kmemleak_alloc+0x28/0x50
>    [<ffffffffa89a89b6>] kmem_cache_alloc_trace+0x1e6/0x550
>    [<ffffffffaa102827>] tcf_chain_create+0x97/0x460
>    [<ffffffffaa102f67>] tcf_block_get+0x127/0x230
>    [<ffffffffc03e8546>] ingress_init+0x76/0x110 [sch_ingress]
>    [<ffffffffaa0fbb1c>] qdisc_create+0x2ec/0x1100
>    [<ffffffffaa0fce1a>] tc_modify_qdisc+0x4ea/0x1ae0
>    [<ffffffffaa0355dc>] rtnetlink_rcv_msg+0xa3c/0x1400
>    [<ffffffffaa12e3cb>] netlink_rcv_skb+0x22b/0x4e0
>    [<ffffffffaa024b55>] rtnetlink_rcv+0x15/0x20
>    [<ffffffffaa12bddd>] netlink_unicast+0x47d/0x710
>    [<ffffffffaa12caef>] netlink_sendmsg+0xa7f/0x1140
>    [<ffffffffa9f15c52>] sock_sendmsg+0xe2/0x170
>    [<ffffffffa9f188bd>] ___sys_sendmsg+0x72d/0xcc0
>    [<ffffffffa9f1bfa2>] __sys_sendmsg+0xe2/0x260
>    [<ffffffffa9f1c132>] SyS_sendmsg+0x12/0x20
>unreferenced object 0xffff8803fd855a08 (size 64):
>  comm "tc", pid 2663, jiffies 4294992152 (age 1299.328s)
>  hex dump (first 32 bytes):
>    00 00 00 00 00 00 00 00 20 49 80 31 07 88 ff ff  ........ I.1....
>    18 5a 85 fd 03 88 ff ff 18 5a 85 fd 03 88 ff ff  .Z.......Z......
>  backtrace:
>    [<ffffffffaa6b0118>] kmemleak_alloc+0x28/0x50
>    [<ffffffffa89a89b6>] kmem_cache_alloc_trace+0x1e6/0x550
>    [<ffffffffaa102827>] tcf_chain_create+0x97/0x460
>    [<ffffffffaa102f67>] tcf_block_get+0x127/0x230
>    [<ffffffffc03e8546>] ingress_init+0x76/0x110 [sch_ingress]
>    [<ffffffffaa0fbb1c>] qdisc_create+0x2ec/0x1100
>    [<ffffffffaa0fce1a>] tc_modify_qdisc+0x4ea/0x1ae0
>    [<ffffffffaa0355dc>] rtnetlink_rcv_msg+0xa3c/0x1400
>    [<ffffffffaa12e3cb>] netlink_rcv_skb+0x22b/0x4e0
>    [<ffffffffaa024b55>] rtnetlink_rcv+0x15/0x20
>    [<ffffffffaa12bddd>] netlink_unicast+0x47d/0x710
>    [<ffffffffaa12caef>] netlink_sendmsg+0xa7f/0x1140
>    [<ffffffffa9f15c52>] sock_sendmsg+0xe2/0x170
>    [<ffffffffa9f188bd>] ___sys_sendmsg+0x72d/0xcc0
>    [<ffffffffa9f1bfa2>] __sys_sendmsg+0xe2/0x260
>    [<ffffffffa9f1c132>] SyS_sendmsg+0x12/0x20
>unreferenced object 0xffff88071b096f28 (size 64):
>  comm "tc", pid 2943, jiffies 4295013397 (age 1214.352s)
>  hex dump (first 32 bytes):
>    00 00 00 00 00 00 00 00 c0 37 e7 30 07 88 ff ff  .........7.0....
>    38 6f 09 1b 07 88 ff ff 38 6f 09 1b 07 88 ff ff  8o......8o......
>  backtrace:
>    [<ffffffffaa6b0118>] kmemleak_alloc+0x28/0x50
>    [<ffffffffa89a89b6>] kmem_cache_alloc_trace+0x1e6/0x550
>    [<ffffffffaa102827>] tcf_chain_create+0x97/0x460
>    [<ffffffffaa102f67>] tcf_block_get+0x127/0x230
>    [<ffffffffc03e8546>] ingress_init+0x76/0x110 [sch_ingress]
>    [<ffffffffaa0fbb1c>] qdisc_create+0x2ec/0x1100
>    [<ffffffffaa0fce1a>] tc_modify_qdisc+0x4ea/0x1ae0
>    [<ffffffffaa0355dc>] rtnetlink_rcv_msg+0xa3c/0x1400
>    [<ffffffffaa12e3cb>] netlink_rcv_skb+0x22b/0x4e0
>    [<ffffffffaa024b55>] rtnetlink_rcv+0x15/0x20
>    [<ffffffffaa12bddd>] netlink_unicast+0x47d/0x710
>    [<ffffffffaa12caef>] netlink_sendmsg+0xa7f/0x1140
>    [<ffffffffa9f15c52>] sock_sendmsg+0xe2/0x170
>    [<ffffffffa9f188bd>] ___sys_sendmsg+0x72d/0xcc0
>    [<ffffffffa9f1bfa2>] __sys_sendmsg+0xe2/0x260
>    [<ffffffffa9f1c132>] SyS_sendmsg+0x12/0x20
>unreferenced object 0xffff880731f66568 (size 64):
>  comm "tc", pid 3263, jiffies 4295033366 (age 1134.480s)
>  hex dump (first 32 bytes):
>    00 00 00 00 00 00 00 00 00 95 64 65 07 88 ff ff  ..........de....
>    78 65 f6 31 07 88 ff ff 78 65 f6 31 07 88 ff ff  xe.1....xe.1....
>  backtrace:
>    [<ffffffffaa6b0118>] kmemleak_alloc+0x28/0x50
>    [<ffffffffa89a89b6>] kmem_cache_alloc_trace+0x1e6/0x550
>    [<ffffffffaa102827>] tcf_chain_create+0x97/0x460
>    [<ffffffffaa102f67>] tcf_block_get+0x127/0x230
>    [<ffffffffc03e8546>] ingress_init+0x76/0x110 [sch_ingress]
>    [<ffffffffaa0fbb1c>] qdisc_create+0x2ec/0x1100
>    [<ffffffffaa0fce1a>] tc_modify_qdisc+0x4ea/0x1ae0
>    [<ffffffffaa0355dc>] rtnetlink_rcv_msg+0xa3c/0x1400
>    [<ffffffffaa12e3cb>] netlink_rcv_skb+0x22b/0x4e0
>    [<ffffffffaa024b55>] rtnetlink_rcv+0x15/0x20
>    [<ffffffffaa12bddd>] netlink_unicast+0x47d/0x710
>    [<ffffffffaa12caef>] netlink_sendmsg+0xa7f/0x1140
>    [<ffffffffa9f15c52>] sock_sendmsg+0xe2/0x170
>    [<ffffffffa9f188bd>] ___sys_sendmsg+0x72d/0xcc0
>    [<ffffffffa9f1bfa2>] __sys_sendmsg+0xe2/0x260
>    [<ffffffffa9f1c132>] SyS_sendmsg+0x12/0x20

  reply	other threads:[~2017-09-05 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 10:54 [PATCH net] net: sched: don't use GFP_KERNEL under spin lock Jakub Kicinski
2017-09-05 10:59 ` Jakub Kicinski
2017-09-05 12:52   ` Jiri Pirko [this message]
2017-09-05 14:25     ` [oss-drivers] " Jakub Kicinski
2017-09-05 14:31       ` Jiri Pirko
2017-09-05 14:10 ` Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170905125221.GA7936@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=kubakici@wp.pl \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).