From: David Ahern <dsahern@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
davem@davemloft.net, yoshfuji@linux-ipv6.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
tgraf@suug.ch, lokesh.dhoundiyal@alliedtelesis.co.nz
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net PATCH] ipv4: drop dst in multicast routing path
Date: Thu, 5 May 2022 20:28:16 -0700 [thread overview]
Message-ID: <366d529e-6149-423a-e012-dbfd9c41baac@kernel.org> (raw)
In-Reply-To: <20220505020017.3111846-1-chris.packham@alliedtelesis.co.nz>
On 5/4/22 7:00 PM, Chris Packham wrote:
> From: Lokesh Dhoundiyal <lokesh.dhoundiyal@alliedtelesis.co.nz>
>
> kmemleak reports the following when routing multicast traffic over an
> ipsec tunnel.
>
> Kmemleak output:
> unreferenced object 0x8000000044bebb00 (size 256):
> comm "softirq", pid 0, jiffies 4294985356 (age 126.810s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 80 00 00 00 05 13 74 80 ..............t.
> 80 00 00 00 04 9b bf f9 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<00000000f83947e0>] __kmalloc+0x1e8/0x300
> [<00000000b7ed8dca>] metadata_dst_alloc+0x24/0x58
> [<0000000081d32c20>] __ipgre_rcv+0x100/0x2b8
> [<00000000824f6cf1>] gre_rcv+0x178/0x540
> [<00000000ccd4e162>] gre_rcv+0x7c/0xd8
> [<00000000c024b148>] ip_protocol_deliver_rcu+0x124/0x350
> [<000000006a483377>] ip_local_deliver_finish+0x54/0x68
> [<00000000d9271b3a>] ip_local_deliver+0x128/0x168
> [<00000000bd4968ae>] xfrm_trans_reinject+0xb8/0xf8
> [<0000000071672a19>] tasklet_action_common.isra.16+0xc4/0x1b0
> [<0000000062e9c336>] __do_softirq+0x1fc/0x3e0
> [<00000000013d7914>] irq_exit+0xc4/0xe0
> [<00000000a4d73e90>] plat_irq_dispatch+0x7c/0x108
> [<000000000751eb8e>] handle_int+0x16c/0x178
> [<000000001668023b>] _raw_spin_unlock_irqrestore+0x1c/0x28
>
> The metadata dst is leaked when ip_route_input_mc() updates the dst for
> the skb. Commit f38a9eb1f77b ("dst: Metadata destinations") correctly
> handled dropping the dst in ip_route_input_slow() but missed the
> multicast case which is handled by ip_route_input_mc(). Drop the dst in
> ip_route_input_mc() avoiding the leak.
>
> Fixes: f38a9eb1f77b ("dst: Metadata destinations")
> Signed-off-by: Lokesh Dhoundiyal <lokesh.dhoundiyal@alliedtelesis.co.nz>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>
> Notes:
> We started seeing this leak in our scenario after commit c0d59da79534
> ("ip_gre: Make none-tun-dst gre tunnel store tunnel info as metadat_dst
> in recv") but there may be other paths that hit the leak so I've set the
> fixes tag as f38a9eb1f77b ("dst: Metadata destinations").
>
> net/ipv4/route.c | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2022-05-06 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 2:00 [net PATCH] ipv4: drop dst in multicast routing path Chris Packham
2022-05-06 3:28 ` David Ahern [this message]
2022-05-06 19:50 ` patchwork-bot+netdevbpf
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=366d529e-6149-423a-e012-dbfd9c41baac@kernel.org \
--to=dsahern@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokesh.dhoundiyal@alliedtelesis.co.nz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tgraf@suug.ch \
--cc=yoshfuji@linux-ipv6.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.