linux-kernel - Re: [PROBLEM] mm : kmemleaks related detected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Wed, 2 Dec 2020 18:47:18 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     Jeffrin Jose T <jeffrin@...agiritech.edu.in>
Cc:     catalin.marinas@....com, Andrew Morton <akpm@...ux-foundation.org>,
        linux-mm@...ck.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PROBLEM] mm :  kmemleaks  related detected

On Thu, Dec 03, 2020 at 12:04:22AM +0530, Jeffrin Jose T wrote:
> hello,
> 
> 
> 2 new suspected  memory leaks.   See  below...

You've reported this to the wrong place.  It looks like the HID
driver would be the place which is leaking memory, and is probably
a better place to report it.

> ------------------x-------------------x------------------------------
> $sudo cat /sys/kernel/debug/kmemleak
> [sudo] password for jeffrin: 
> unreferenced object 0xffff88813128bee0 (size 16):
> comm "irq/109-ELAN130", pid 152, jiffies 4294931163 (age 9576.624s)
> hex dump (first 16 bytes):
> 04 03 08 0a eb 03 24 e7 01 80 13 44 00 00 00 00 ......$....D....
> backtrace:
> [<00000000eff80361>] kmemdup+0x1a/0x40
> [<00000000552197bd>] hidraw_report_event+0xbc/0x190 [hid]
> [<00000000a102ccd5>] hid_report_raw_event+0x70a/0x790 [hid]
> [<00000000b1b8f73f>] hid_input_report+0x1b4/0x210 [hid]
> [<00000000e0f74a09>] i2c_hid_irq+0x164/0x1e0 [i2c_hid]
> [<00000000a79c6ce4>] irq_thread_fn+0x40/0xb0
> [<0000000037a84810>] irq_thread+0x23d/0x330
> [<0000000009e057aa>] kthread+0x1cd/0x1f0
> [<000000005e7b7b46>] ret_from_fork+0x22/0x30
> unreferenced object 0xffff88813128b640 (size 16):
> comm "irq/109-ELAN130", pid 152, jiffies 4294931165 (age 9576.616s)
> hex dump (first 16 bytes):
> 04 03 02 0a ee 03 74 e7 01 80 13 44 00 00 00 00 ......t....D....
> backtrace:
> [<00000000eff80361>] kmemdup+0x1a/0x40
> [<00000000552197bd>] hidraw_report_event+0xbc/0x190 [hid]
> [<00000000a102ccd5>] hid_report_raw_event+0x70a/0x790 [hid]
> [<00000000b1b8f73f>] hid_input_report+0x1b4/0x210 [hid]
> [<00000000e0f74a09>] i2c_hid_irq+0x164/0x1e0 [i2c_hid]
> [<00000000a79c6ce4>] irq_thread_fn+0x40/0xb0
> [<0000000037a84810>] irq_thread+0x23d/0x330
> [<0000000009e057aa>] kthread+0x1cd/0x1f0
> [<000000005e7b7b46>] ret_from_fork+0x22/0x30
> $
> ----------------------x-----------------x------------------------x-----
> ------------

> Reported-by: Jeffrin Jose T <jeffrin@...agiritech.edu.in>
> Tested-by: Jeffrin Jose T <jeffrin@...agiritech.edu.in>

Tested-by is used to indicate that you tested the patch.  Since there
is no patch yet, you can't have tested it.