From: Sven Eckelmann <sven@narfation.org>
To: linus.luessing@c0d3.blue
Cc: b.a.t.m.a.n@lists.open-mesh.org, clm@fb.com, davem@davemloft.net,
dsterba@suse.com, edumazet@google.com, josef@toxicpanda.com,
kuba@kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com,
syzbot <syzbot+ebe64cc5950868e77358@syzkaller.appspotmail.com>
Subject: Re: [syzbot] [btrfs?] memory leak in corrupted
Date: Tue, 16 Jan 2024 10:48:03 +0100 [thread overview]
Message-ID: <23660052.EfDdHjke4D@ripper> (raw)
In-Reply-To: <000000000000beadc4060f0cbc23@google.com>
[-- Attachment #1: Type: text/plain, Size: 3838 bytes --]
@Linus, this looks like something for you.
On Tuesday, 16 January 2024 10:27:20 CET syzbot wrote:
> syzbot found the following issue on:
>
> HEAD commit: 052d534373b7 Merge tag 'exfat-for-6.8-rc1' of git://git.ke..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14620debe80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a7031f9e71583b4a
> dashboard link: https://syzkaller.appspot.com/bug?extid=ebe64cc5950868e77358
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a344c1e80000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/82a7201eef4c/disk-052d5343.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/ca12b4c31826/vmlinux-052d5343.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/3f07360ba5a8/bzImage-052d5343.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+ebe64cc5950868e77358@syzkaller.appspotmail.com
The relevant line is the batadv_mcast_forw_tracker_tvlv_handler registration
in batadv_mcast_init() which was introduced in
commit 07afe1ba288c ("batman-adv: mcast: implement multicast packet reception and forwarding")
And I can't find the batadv_tvlv_handler_unregister for
BATADV_TVLV_MCAST_TRACKER in batadv_mcast_free()
Kind regards,
Sven
>
> BUG: memory leak
> unreferenced object 0xffff88811c71a980 (size 64):
> comm "syz-executor.7", pid 5063, jiffies 4294953937
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 20 8e 7e 1c 81 88 ff ff ........ .~.....
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc 9f8721dd):
> [<ffffffff815f7d53>] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline]
> [<ffffffff815f7d53>] slab_post_alloc_hook mm/slub.c:3817 [inline]
> [<ffffffff815f7d53>] slab_alloc_node mm/slub.c:3860 [inline]
> [<ffffffff815f7d53>] kmalloc_trace+0x283/0x330 mm/slub.c:4007
> [<ffffffff84aae617>] kmalloc include/linux/slab.h:590 [inline]
> [<ffffffff84aae617>] kzalloc include/linux/slab.h:711 [inline]
> [<ffffffff84aae617>] batadv_tvlv_handler_register+0xf7/0x2a0 net/batman-adv/tvlv.c:560
> [<ffffffff84a8d09f>] batadv_mcast_init+0x4f/0xc0 net/batman-adv/multicast.c:1926
> [<ffffffff84a895b9>] batadv_mesh_init+0x209/0x2f0 net/batman-adv/main.c:231
> [<ffffffff84a9fa88>] batadv_softif_init_late+0x1f8/0x280 net/batman-adv/soft-interface.c:812
> [<ffffffff83f48559>] register_netdevice+0x189/0xca0 net/core/dev.c:10188
> [<ffffffff84a9f255>] batadv_softif_newlink+0x55/0x70 net/batman-adv/soft-interface.c:1088
> [<ffffffff83f61dc0>] rtnl_newlink_create net/core/rtnetlink.c:3515 [inline]
> [<ffffffff83f61dc0>] __rtnl_newlink+0xb10/0xec0 net/core/rtnetlink.c:3735
> [<ffffffff83f621bc>] rtnl_newlink+0x4c/0x70 net/core/rtnetlink.c:3748
> [<ffffffff83f5cd1f>] rtnetlink_rcv_msg+0x22f/0x5b0 net/core/rtnetlink.c:6615
> [<ffffffff84093291>] netlink_rcv_skb+0x91/0x1d0 net/netlink/af_netlink.c:2543
> [<ffffffff84092242>] netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]
> [<ffffffff84092242>] netlink_unicast+0x2c2/0x440 net/netlink/af_netlink.c:1367
> [<ffffffff84092701>] netlink_sendmsg+0x341/0x690 net/netlink/af_netlink.c:1908
> [<ffffffff83ef2912>] sock_sendmsg_nosec net/socket.c:730 [inline]
> [<ffffffff83ef2912>] __sock_sendmsg+0x52/0xa0 net/socket.c:745
> [<ffffffff83ef5af4>] __sys_sendto+0x164/0x1e0 net/socket.c:2191
> [<ffffffff83ef5b98>] __do_sys_sendto net/socket.c:2203 [inline]
> [<ffffffff83ef5b98>] __se_sys_sendto net/socket.c:2199 [inline]
> [<ffffffff83ef5b98>] __x64_sys_sendto+0x28/0x30 net/socket.c:2199
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-16 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 9:27 [syzbot] [btrfs?] memory leak in corrupted syzbot
2024-01-16 9:48 ` Sven Eckelmann [this message]
2024-01-17 9:30 ` Sven Eckelmann
2024-01-17 10:00 ` syzbot
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=23660052.EfDdHjke4D@ripper \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=dsterba@suse.com \
--cc=edumazet@google.com \
--cc=josef@toxicpanda.com \
--cc=kuba@kernel.org \
--cc=linus.luessing@c0d3.blue \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+ebe64cc5950868e77358@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 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.