linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Sagi Grimberg <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: Kmemleak on nvme-6.5
Date: Wed, 17 May 2023 07:51:08 +0000	[thread overview]
Message-ID: <ef810b97-cd2c-50c6-c3a0-15681b4679be@nvidia.com> (raw)
In-Reply-To: <470d8e75-c2a2-ed21-6cd4-fc06d0b80e97@grimberg.me>

On 5/17/23 00:47, Sagi Grimberg wrote:
>
>> Hi,
>>
>> I've observed following kmemleak on nvme-6.5 with blktests
>> nvme/003 HEAD:-
>>
>> nvme (nvme-6.5) # git log
>> commit 851c23be6fc95a48dbdac864f18be63f9a41e8a8 (HEAD -> nvme-6.5,
>> origin/nvme-6.5)
>> Author: Max Gurtovoy <mgurtovoy@nvidia.com>
>> Date:   Tue Apr 25 00:12:42 2023 +0300
>>
>>       nvme: move sysfs code to a dedicated sysfs.c file
>
> I'm assuming this is not the result of a bisect correct?

no it's current head on which I ran blktests ..

-ck



  reply	other threads:[~2023-05-17  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  5:35 Kmemleak on nvme-6.5 Chaitanya Kulkarni
2023-05-17  7:47 ` Sagi Grimberg
2023-05-17  7:51   ` Chaitanya Kulkarni [this message]
2023-06-04  6:38 ` Chaitanya Kulkarni
2023-06-04  6:42   ` Chaitanya Kulkarni

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=ef810b97-cd2c-50c6-c3a0-15681b4679be@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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;
as well as URLs for NNTP newsgroup(s).