From: Jens Axboe <axboe@kernel.dk>
To: Chen Jun <chenjun102@huawei.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
will@kernel.org, ming.lei@redhat.com
Cc: xuqiang36@huawei.com
Subject: Re: [PATCH] blk-mq: Fix kmemleak in blk_mq_init_allocated_queue
Date: Mon, 31 Oct 2022 08:31:07 -0600 [thread overview]
Message-ID: <166722666769.125558.7022234189834891609.b4-ty@kernel.dk> (raw)
In-Reply-To: <20221031031242.94107-1-chenjun102@huawei.com>
On Mon, 31 Oct 2022 03:12:42 +0000, Chen Jun wrote:
> There is a kmemleak caused by modprobe null_blk.ko
>
> unreferenced object 0xffff8881acb1f000 (size 1024):
> comm "modprobe", pid 836, jiffies 4294971190 (age 27.068s)
> hex dump (first 32 bytes):
> 00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........
> ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff .........S......
> backtrace:
> [<000000004a10c249>] kmalloc_node_trace+0x22/0x60
> [<00000000648f7950>] blk_mq_alloc_and_init_hctx+0x289/0x350
> [<00000000af06de0e>] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0
> [<00000000e00c1872>] blk_mq_init_allocated_queue+0x48c/0x1440
> [<00000000d16b4e68>] __blk_mq_alloc_disk+0xc8/0x1c0
> [<00000000d10c98c3>] 0xffffffffc450d69d
> [<00000000b9299f48>] 0xffffffffc4538392
> [<0000000061c39ed6>] do_one_initcall+0xd0/0x4f0
> [<00000000b389383b>] do_init_module+0x1a4/0x680
> [<0000000087cf3542>] load_module+0x6249/0x7110
> [<00000000beba61b8>] __do_sys_finit_module+0x140/0x200
> [<00000000fdcfff51>] do_syscall_64+0x35/0x80
> [<000000003c0f1f71>] entry_SYSCALL_64_after_hwframe+0x46/0xb0
>
> [...]
Applied, thanks!
[1/1] blk-mq: Fix kmemleak in blk_mq_init_allocated_queue
commit: 943f45b9399ed8b2b5190cbc797995edaa97f58f
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-10-31 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 3:12 Chen Jun
2022-10-31 14:07 ` Ming Lei
2022-10-31 14:31 ` Jens Axboe [this message]
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=166722666769.125558.7022234189834891609.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=chenjun102@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=will@kernel.org \
--cc=xuqiang36@huawei.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
all inboxes | Powered by JetHome®