All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Jens Axboe <axboe@kernel.dk>, Yi Zhang <yi.zhang@redhat.com>,
	linux-block <linux-block@vger.kernel.org>,
	Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [bug report] kmemleak issue observed during blktests
Date: Wed, 16 Jul 2025 18:40:10 +0800	[thread overview]
Message-ID: <aHeBiu9pHZwO95vW@fedora> (raw)
In-Reply-To: <08f3f802-e3c3-b851-b4ee-912eade04c6f@huaweicloud.com>

On Wed, Jul 16, 2025 at 03:50:34PM +0800, Yu Kuai wrote:
> Hi,
> 
> 在 2025/07/16 9:54, Jens Axboe 写道:
> > 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]
> 
> This is werid, and I check the code that it's impossible
> blk_mq_update_nr_hw_queues() can be called from find_fallback().

Yes.

> Does kmemleak show wrong backtrace?

I tried to run blktests block/005 over nbd, but can't reproduce this
kmemleak report after setting up the detector.

Yi, can you share your reproducer?


Thanks
Ming


  reply	other threads:[~2025-07-16 10:40 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
2025-07-16  7:50   ` Yu Kuai
2025-07-16 10:40     ` Ming Lei [this message]
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=aHeBiu9pHZwO95vW@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yi.zhang@redhat.com \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@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 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.