From: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
To: linux-gpio@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-kernel@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: INFO: memory leak in gpio device in 6.2-rc6
Date: Tue, 31 Jan 2023 10:36:55 +0100 [thread overview]
Message-ID: <cdb562c5-040e-687f-a61f-4273fc356ff3@alu.unizg.hr> (raw)
Hi all,
I came across this memory leak apparently in the GPIO device driver.
It is still present in 6.2-rc6 release candidate kernel (just ran kselftest).
This is a vanilla Torvalds tree kernel with MGLRU and KMEMLEAK (obviously)
enabled.
If you think this bug is significant, I can attempt the bug bisect in the
environment that triggered it (Lenovo LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB)
with BIOS M22KT49A from 11/10/2022 and AlmaLinux 8.7.
Here is the /sys/kernel/debug/kmemleak output:
unreferenced object 0xffff9e67ad71f160 (size 32):
comm "gpio-sim.sh", pid 208926, jiffies 4372229685 (age 2101.564s)
hex dump (first 32 bytes):
67 70 69 6f 2d 73 69 6d 2e 30 2d 6e 6f 64 65 30 gpio-sim.0-node0
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<0000000098bf3d1b>] slab_post_alloc_hook+0x91/0x320
[<00000000da3205c5>] __kmem_cache_alloc_node+0x1bf/0x2b0
[<00000000aa51a58a>] __kmalloc_node_track_caller+0x55/0x140
[<00000000bd682ecc>] kvasprintf+0x6b/0xd0
[<00000000a3431d55>] kasprintf+0x4e/0x70
[<00000000f52d2629>] gpio_sim_device_config_live_store+0x401/0x59d [gpio_sim]
[<00000000673fc6df>] configfs_write_iter+0xcc/0x130
[<000000001d5d0829>] vfs_write+0x2b4/0x3d0
[<00000000d2336251>] ksys_write+0x61/0xe0
[<00000000f7015bb1>] __x64_sys_write+0x1a/0x20
[<000000008ac743d2>] do_syscall_64+0x58/0x80
[<000000004d7b7d50>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
[root@pc-mtodorov marvin]#
Regards,
Mirsad
--
Mirsad Todorovac
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb
Republic of Croatia, the European Union
--
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
next reply other threads:[~2023-01-31 9:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 9:36 Mirsad Goran Todorovac [this message]
2023-02-08 19:55 ` INFO: REPRODUCED: memory leak in gpio device in 6.2-rc6 Mirsad Goran Todorovac
2023-02-12 14:19 ` Andy Shevchenko
2023-02-14 18:19 ` Mirsad Goran Todorovac
2023-02-15 10:53 ` Andy Shevchenko
2023-02-15 14:45 ` Mirsad Goran Todorovac
2023-02-16 14:16 ` Bartosz Golaszewski
2023-02-20 13:10 ` Mirsad Todorovac
2023-02-20 13:43 ` Andy Shevchenko
2023-02-21 13:52 ` Mirsad Goran Todorovac
2023-02-21 14:20 ` Mirsad Goran Todorovac
2023-02-21 14:32 ` Mirsad Goran Todorovac
2023-02-21 15:39 ` Andy Shevchenko
2023-02-22 10:53 ` Bartosz Golaszewski
2023-02-22 21:27 ` Mirsad Goran Todorovac
2023-02-24 15:12 ` Mirsad Todorovac
2023-02-24 17:40 ` Andy Shevchenko
2023-02-27 18:38 ` Mirsad Todorovac
2023-02-27 23:13 ` Andy Shevchenko
2023-03-08 13:11 ` Mirsad Todorovac
2023-03-08 15:20 ` Andy Shevchenko
2023-03-08 23:17 ` Mirsad Goran Todorovac
2023-02-14 20:54 ` INFO: BISECTED: " Mirsad Goran Todorovac
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=cdb562c5-040e-687f-a61f-4273fc356ff3@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
/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).