From: Jens Axboe <axboe@kernel.dk>
To: Yi Zhang <yi.zhang@redhat.com>,
linux-block <linux-block@vger.kernel.org>
Cc: Ming Lei <ming.lei@redhat.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [bug report] kmemleak issue observed during blktests
Date: Tue, 15 Jul 2025 19:54:14 -0600 [thread overview]
Message-ID: <d52a8216-dd70-4489-a645-55d174bcdd9e@kernel.dk> (raw)
In-Reply-To: <CAHj4cs8oJFvz=daCvjHM5dYCNQH4UXwSySPPU4v-WHce_kZXZA@mail.gmail.com>
On 7/15/25 7:42 PM, Yi Zhang wrote:
> Hi
>
> I found the following kmemleak issue on the latest
> linux-block/for-next, please help check it and let me know if you need
> any info/testing for it, thanks.
>
> commit: linux-block/for-next: 8192f418ee2f (HEAD -> for-next,
> origin/for-next) Merge branch 'for-6.17/io_uring' into for-next
>
> # dmesg | grep kmemleak
> [31404.993877] kmemleak: 608 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
>
> unreferenced object 0xffff8882e7fb9000 (size 2048):
> comm "check", pid 10460, jiffies 4324980514
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc c47e6a37):
> __kvmalloc_node_noprof+0x55d/0x7a0
> sbitmap_init_node+0x15a/0x6a0
> kyber_init_hctx+0x316/0xb90
> blk_mq_init_sched+0x416/0x580
> elevator_switch+0x18b/0x630
> elv_update_nr_hw_queues+0x219/0x2c0
> __blk_mq_update_nr_hw_queues+0x36a/0x6f0
> blk_mq_update_nr_hw_queues+0x3a/0x60
> find_fallback+0x510/0x540 [nbd]
> nbd_send_cmd+0x24b/0x1480 [nbd]
> configfs_write_iter+0x2ae/0x470
> vfs_write+0x524/0xe70
> ksys_write+0xff/0x200
> do_syscall_64+0x98/0x3c0
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
> unreferenced object 0xffff8882e7fbb000 (size 2048):
> comm "check", pid 10460, jiffies 4324980514
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc c47e6a37):
> __kvmalloc_node_noprof+0x55d/0x7a0
> sbitmap_init_node+0x15a/0x6a0
> kyber_init_hctx+0x316/0xb90
> blk_mq_init_sched+0x416/0x580
> elevator_switch+0x18b/0x630
> elv_update_nr_hw_queues+0x219/0x2c0
> __blk_mq_update_nr_hw_queues+0x36a/0x6f0
> blk_mq_update_nr_hw_queues+0x3a/0x60
> find_fallback+0x510/0x540 [nbd]
> nbd_send_cmd+0x24b/0x1480 [nbd]
> configfs_write_iter+0x2ae/0x470
> vfs_write+0x524/0xe70
> ksys_write+0xff/0x200
> do_syscall_64+0x98/0x3c0
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
> unreferenced object 0xffff88819e855000 (size 2048):
> comm "check", pid 10460, jiffies 4324980514
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc c47e6a37):
> __kvmalloc_node_noprof+0x55d/0x7a0
> sbitmap_init_node+0x15a/0x6a0
> kyber_init_hctx+0x316/0xb90
> blk_mq_init_sched+0x416/0x580
> elevator_switch+0x18b/0x630
> elv_update_nr_hw_queues+0x219/0x2c0
> __blk_mq_update_nr_hw_queues+0x36a/0x6f0
> blk_mq_update_nr_hw_queues+0x3a/0x60
> find_fallback+0x510/0x540 [nbd]
> nbd_send_cmd+0x24b/0x1480 [nbd]
> configfs_write_iter+0x2ae/0x470
> vfs_write+0x524/0xe70
> ksys_write+0xff/0x200
> do_syscall_64+0x98/0x3c0
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
Can you try and revert:
commit 8b428f42f3edfd62422aa7ad87049ab232a2eaa9
Author: Ming Lei <ming.lei@redhat.com>
Date: Wed Jul 9 19:17:44 2025 +0800
nbd: fix lockdep deadlock warning
and see if that fixes it? If not, then checkout for-6.17/block instead,
and then run a bisect with that sha marked as bad, and v6.16-rc4 as the
known good one.
--
Jens Axboe
next prev parent reply other threads:[~2025-07-16 1:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 1:42 [bug report] kmemleak issue observed during blktests Yi Zhang
2025-07-16 1:54 ` Jens Axboe [this message]
2025-07-16 7:50 ` Yu Kuai
2025-07-16 10:40 ` Ming Lei
2025-07-16 19:24 ` Nilay Shroff
2025-07-17 0:02 ` Ming Lei
2025-07-17 0:46 ` Yi Zhang
2025-07-17 14:22 ` Nilay Shroff
2025-07-17 14:11 ` Nilay Shroff
2025-07-17 14:25 ` Yi Zhang
2025-07-17 14:28 ` Nilay Shroff
2025-07-17 3:58 ` Yi Zhang
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=d52a8216-dd70-4489-a645-55d174bcdd9e@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yi.zhang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.