From: Keith Busch <kbusch@kernel.org>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: Sagi Grimberg <sagi@grimberg.me>, Yi Zhang <yi.zhang@redhat.com>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: blktests nvme 041,042 leak memory
Date: Thu, 30 May 2024 10:29:47 -0600 [thread overview]
Message-ID: <Zlipe2FVAIRmas1e@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <CAFL455=ixC0S8aU+AouQFtDFN0bFdNgSXH0d9a2-VXegj8dPuQ@mail.gmail.com>
On Thu, May 30, 2024 at 09:25:24AM +0200, Maurizio Lombardi wrote:
> ct 30. 5. 2024 v 8:59 odesílatel Sagi Grimberg <sagi@grimberg.me> napsal:
> >
> >
> > Lets just do that... and add a comment that we don't want to add
> > function calls that can fail post cdev_device_add() because we have a
> > cleanup problem (with a short explanation), so this is less likely to
> > come back...
> >
>
> Solution 1 will work even if it's not 100% perfect because after
> calling device_initialize()
> you're supposed to use put_device() to release the instance and not
> free the dev directly.
>
> (The nvme_put_ctrl() call in the error path just releases the
> additional reference taken
> by nvme_get_ctrl() just before the call to cdev_device_add()).
I noticed that too, if cdev_dev_add() fails we are supposed to do a
put_device. This driver seems to be making it difficult to use the core
device interfaces as intended.
next prev parent reply other threads:[~2024-05-30 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 19:47 blktests nvme 041,042 leak memory Sagi Grimberg
2024-05-27 1:11 ` Yi Zhang
2024-05-28 9:44 ` Maurizio Lombardi
2024-05-29 9:08 ` Maurizio Lombardi
2024-05-29 12:51 ` Sagi Grimberg
2024-05-29 13:45 ` Maurizio Lombardi
2024-05-29 16:25 ` Keith Busch
2024-05-29 16:48 ` Keith Busch
2024-05-30 6:59 ` Sagi Grimberg
2024-05-30 7:25 ` Maurizio Lombardi
2024-05-30 16:29 ` Keith Busch [this message]
2024-05-30 17:40 ` Maurizio Lombardi
2024-05-31 11:55 ` Maurizio Lombardi
2024-05-31 14:37 ` Maurizio Lombardi
2024-06-03 8:37 ` Hannes Reinecke
2024-06-03 8:52 ` Maurizio Lombardi
2024-06-03 9:33 ` Hannes Reinecke
2024-06-03 9:38 ` Maurizio Lombardi
2024-06-03 9:35 ` Maurizio Lombardi
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=Zlipe2FVAIRmas1e@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.com \
--cc=sagi@grimberg.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox