From: syzbot <syzbot+7a942657a255a9d9b18a@syzkaller.appspotmail.com>
To: code@siddh.me, davem@davemloft.net, johannes@sipsolutions.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in cfg80211_inform_single_bss_frame_data
Date: Wed, 13 Jul 2022 02:08:08 -0700 [thread overview]
Message-ID: <000000000000a4271f05e3ac1ff8@google.com> (raw)
In-Reply-To: <181f6c7ee61.6fd1462c198214.9029235269763018181@siddh.me>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in regulatory_init_db
BUG: memory leak
unreferenced object 0xffff8881450dc880 (size 64):
comm "swapper/0", pid 1, jiffies 4294937974 (age 80.900s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
ff ff ff ff 00 00 00 00 00 00 00 00 30 30 00 00 ............00..
backtrace:
[<ffffffff86ff026b>] kmalloc include/linux/slab.h:600 [inline]
[<ffffffff86ff026b>] kzalloc include/linux/slab.h:733 [inline]
[<ffffffff86ff026b>] regulatory_hint_core net/wireless/reg.c:3216 [inline]
[<ffffffff86ff026b>] regulatory_init_db+0x22f/0x2de net/wireless/reg.c:4277
[<ffffffff81000fe3>] do_one_initcall+0x63/0x2e0 init/main.c:1295
[<ffffffff86f4eb10>] do_initcall_level init/main.c:1368 [inline]
[<ffffffff86f4eb10>] do_initcalls init/main.c:1384 [inline]
[<ffffffff86f4eb10>] do_basic_setup init/main.c:1403 [inline]
[<ffffffff86f4eb10>] kernel_init_freeable+0x255/0x2cf init/main.c:1610
[<ffffffff845b427a>] kernel_init+0x1a/0x1c0 init/main.c:1499
[<ffffffff8100225f>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
[ 88.
Tested on:
commit: b047602d Merge tag 'trace-v5.19-rc5' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13d4252a080000
kernel config: https://syzkaller.appspot.com/x/.config?x=689b5fe7168a1260
dashboard link: https://syzkaller.appspot.com/bug?extid=7a942657a255a9d9b18a
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
next prev parent reply other threads:[~2022-07-13 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 16:37 [syzbot] memory leak in cfg80211_inform_single_bss_frame_data syzbot
2021-10-25 22:33 ` syzbot
2021-10-26 9:27 ` Fabio M. De Francesco
2022-07-13 8:56 ` Siddh Raman Pant
2022-07-13 8:58 ` Siddh Raman Pant
2022-07-13 9:08 ` syzbot [this message]
2022-07-13 10:25 ` Siddh Raman Pant
2022-07-13 10:35 ` 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=000000000000a4271f05e3ac1ff8@google.com \
--to=syzbot+7a942657a255a9d9b18a@syzkaller.appspotmail.com \
--cc=code@siddh.me \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).