public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: linux-block <linux-block@vger.kernel.org>,
	"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>
Subject: Re: [bug report] kmemleak observed from blktests on latest linux-block/for-next
Date: Mon, 13 Jun 2022 11:29:15 +0800	[thread overview]
Message-ID: <YqavC8hwLXwPVnor@T590> (raw)
In-Reply-To: <CAHj4cs8iJPnQ+zGHNTapR9HWMk9nBXUPbhYi5k-vKZf4qRmz_A@mail.gmail.com>

On Sun, Jun 12, 2022 at 03:23:36PM +0800, Yi Zhang wrote:
> Hello
> I found below kmemleak with the latest linux-block/for-next[1], pls
> help check it, thanks.
> 
> [1]
> 75d6654eb3ab (origin/for-next) Merge branch 'for-5.19/block' into for-next

Hi Yi,

for-5.19/block should be stale, and seems not see such issue when running blktests
on v5.19-rc2.


Thanks,
Ming


  reply	other threads:[~2022-06-13  3:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12  7:23 [bug report] kmemleak observed from blktests on latest linux-block/for-next Yi Zhang
2022-06-13  3:29 ` Ming Lei [this message]
2022-06-13 13:08   ` Yi Zhang
2022-06-13 14:23     ` Ming Lei
2022-06-14  5:35       ` Yi Zhang
2022-06-26 14:16         ` Sagi Grimberg

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=YqavC8hwLXwPVnor@T590 \
    --to=ming.lei@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox