kmemleak from bcm2835_v4l2 kernel module
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
Research direction
Reproduce the report on the v5.4 or v5.8 branch with kmemleak, then trace the bcm2835_v4l2 probe path through vchiq_initialise, vchi_initialise, and vchiq_mmal_init as shown in the backtrace. Determine which allocation remains reported and verify that the kmemleak trace no longer appears when the issue is fixed.
Written by the indexing model from the issue text.
Description
I test v5.4 and v5.8 branch, when kernel module bcm2835_v4l2 is loaded, there is below kmemleak trace as below:
backtrace:
[<000000001c7fc46e>] kmem_cache_alloc_trace+0x178/0x3a4
[<00000000726f02dd>] vchiq_initialise+0x84/0x1b0 [vchiq]
[<000000005149603c>] vchi_initialise+0x30/0x5c [vchiq]
[<00000000a39a76ee>] vchiq_mmal_init+0x64/0x1cc [bcm2835_mmal_vchiq]
[<000000002d4a9a0a>] bcm2835_mmal_probe+0x34/0x470 [bcm2835_v4l2]
[<000000004ccd0b13>] platform_drv_probe+0x58/0xac
[<000000006b15ad99>] really_probe+0xe8/0x404
[<00000000e643e6da>] driver_probe_device+0x5c/0xf0
[<0000000001e8d9cc>] device_driver_attach+0xbc/0xc4
[<000000004ac3f57a>] __driver_attach+0x90/0x12c
[<00000000880346db>] bus_for_each_dev+0x80/0xd0
[<0000000042dbfbf7>] driver_attach+0x30/0x3c
[<00000000f7c00732>] bus_add_driver+0x108/0x1ec
[<0000000019ccb753>] driver_register+0x78/0x120
[<000000008ef5b751>] __platform_driver_register+0x54/0x60
[<00000000aa1de3f3>] 0xffffffc008d13028
thanks,
Limeng
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·