From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215197] Memory leaks show up when using Edimax Wi-Fi N150 Bluetooth/Wireless USB Adapter (RTL8XXXU)
Date: Wed, 14 Sep 2022 13:10:52 +0000 [thread overview]
Message-ID: <bug-215197-62941-aM9QzTWrhO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215197-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215197
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Jes.Sorensen@gmail.com
Component|Bluetooth |network-wireless
Summary|Memory leaks show up a |Memory leaks show up when
|while after usung Edimax |using Edimax Wi-Fi N150
|Wi-Fi N150 Bluetooth4.0 USB |Bluetooth/Wireless USB
|Adapter (rtl8723be) |Adapter (RTL8XXXU)
--- Comment #4 from Erhard F. (erhard_f@mailbox.org) ---
Still a problem on v6.0-rc4:
# cat /sys/kernel/debug/kmemleak
unreferenced object 0xffff8b7b18611bc0 (size 216):
comm "iwd", pid 1992, jiffies 4294908755 (age 2333.527s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff9d294858>] kmem_cache_alloc+0x288/0x380
[<ffffffff9d7f161a>] __alloc_skb+0x8a/0x250
[<ffffffff9d7f18cc>] __netdev_alloc_skb+0xec/0x190
[<ffffffffc17f2f1f>] rtl8xxxu_submit_rx_urb+0x4f/0xf0 [rtl8xxxu]
[<ffffffffc17f0641>] rtl8xxxu_start+0x321/0x8b0 [rtl8xxxu]
[<ffffffffc16910dd>] drv_start+0x6d/0x120 [mac80211]
[<ffffffffc16af3e2>] ieee80211_do_open+0x142/0x9c0 [mac80211]
[<ffffffffc16b2279>] ieee80211_open+0x59/0x80 [mac80211]
[<ffffffff9d80ad72>] __dev_open+0x122/0x1f0
[<ffffffff9d815daa>] __dev_change_flags+0xaa/0x200
[<ffffffff9d81613c>] dev_change_flags+0x1c/0x60
[<ffffffff9d83575b>] do_setlink+0x4ab/0x10e0
[<ffffffff9d82f808>] rtnl_setlink+0x218/0x260
[<ffffffff9d834dbf>] rtnetlink_rcv_msg+0x32f/0x5e0
[<ffffffff9d880291>] netlink_rcv_skb+0x101/0x130
[<ffffffff9d87df33>] netlink_unicast+0x1d3/0x2d0
unreferenced object 0xffff8b7b18729a80 (size 216):
comm "iwd", pid 1992, jiffies 4294997204 (age 2038.757s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[...]
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-09-14 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 0:03 [Bug 215197] New: Memory leaks show up a while after usung Edimax Wi-Fi N150 Bluetooth4.0 USB Adapter (rtl8723be) bugzilla-daemon
2021-12-02 0:04 ` [Bug 215197] " bugzilla-daemon
2021-12-02 0:04 ` bugzilla-daemon
2021-12-02 0:07 ` bugzilla-daemon
2021-12-02 0:08 ` bugzilla-daemon
2022-09-14 13:10 ` bugzilla-daemon [this message]
2022-09-14 13:11 ` [Bug 215197] Memory leaks show up when using Edimax Wi-Fi N150 Bluetooth/Wireless USB Adapter (RTL8XXXU) bugzilla-daemon
2022-09-14 13:12 ` bugzilla-daemon
2022-09-14 13:13 ` bugzilla-daemon
2022-11-17 21:22 ` bugzilla-daemon
2022-11-24 12:38 ` bugzilla-daemon
2022-12-09 1:17 ` bugzilla-daemon
2022-12-09 11:29 ` bugzilla-daemon
2022-12-09 11:32 ` bugzilla-daemon
2024-04-29 21:38 ` bugzilla-daemon
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=bug-215197-62941-aM9QzTWrhO@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox