From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Ye Bin <yebin@huaweicloud.com>
Cc: Ye Bin <yebin10@huawei.com>, ming.lei@redhat.com
Subject: Re: [PATCH] blk-mq: fix possible memleak when register 'hctx' failed
Date: Fri, 25 Nov 2022 06:34:26 -0700 [thread overview]
Message-ID: <166938326642.10648.1942082324154053183.b4-ty@kernel.dk> (raw)
In-Reply-To: <20221117022940.873959-1-yebin@huaweicloud.com>
On Thu, 17 Nov 2022 10:29:40 +0800, Ye Bin wrote:
> From: Ye Bin <yebin10@huawei.com>
>
> There's issue as follows when do fault injection test:
> unreferenced object 0xffff888132a9f400 (size 512):
> comm "insmod", pid 308021, jiffies 4324277909 (age 509.733s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 08 f4 a9 32 81 88 ff ff ...........2....
> 08 f4 a9 32 81 88 ff ff 00 00 00 00 00 00 00 00 ...2............
> backtrace:
> [<00000000e8952bb4>] kmalloc_node_trace+0x22/0xa0
> [<00000000f9980e0f>] blk_mq_alloc_and_init_hctx+0x3f1/0x7e0
> [<000000002e719efa>] blk_mq_realloc_hw_ctxs+0x1e6/0x230
> [<000000004f1fda40>] blk_mq_init_allocated_queue+0x27e/0x910
> [<00000000287123ec>] __blk_mq_alloc_disk+0x67/0xf0
> [<00000000a2a34657>] 0xffffffffa2ad310f
> [<00000000b173f718>] 0xffffffffa2af824a
> [<0000000095a1dabb>] do_one_initcall+0x87/0x2a0
> [<00000000f32fdf93>] do_init_module+0xdf/0x320
> [<00000000cbe8541e>] load_module+0x3006/0x3390
> [<0000000069ed1bdb>] __do_sys_finit_module+0x113/0x1b0
> [<00000000a1a29ae8>] do_syscall_64+0x35/0x80
> [<000000009cd878b0>] entry_SYSCALL_64_after_hwframe+0x46/0xb0
>
> [...]
Applied, thanks!
[1/1] blk-mq: fix possible memleak when register 'hctx' failed
commit: 4b7a21c57b14fbcd0e1729150189e5933f5088e9
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-25 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 2:29 Ye Bin
2022-11-17 2:19 ` Ming Lei
2022-11-24 13:44 ` yebin (H)
2022-11-25 13:34 ` 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=166938326642.10648.1942082324154053183.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yebin10@huawei.com \
--cc=yebin@huaweicloud.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®