Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "alan.adamson@oracle.com" <alan.adamson@oracle.com>
Subject: debugfs message during creation of the NVMeOf controller
Date: Thu, 23 Mar 2023 08:18:47 +0000	[thread overview]
Message-ID: <40baa75e-fdf5-cb73-5fa8-b12d65bce4e7@nvidia.com> (raw)

Hi everyone,

Whenever I create NVMeOF target controller using nvme-loop
transport I'm getting following message:-

[18318.052193] debugfs: Directory 'nvme1' with parent '/' already present!
[18318.053164] nvme1: failed to create debugfs attr
[18318.053239] nvmet: creating nvm controller 1 for subsystem testnqn 
for NQN 
nqn.2014-08.org.nvmexpress:uuid:bb0a23ee-0be3-4285-8d8a-b47fcad11fe1.
[18318.053369] nvme nvme1: creating 48 I/O queues.
[18318.058812] nvme nvme1: new ctrl: "testnqn"

It is certainly coming from
host/fault_inject.c:nvme_fault_inject_init().

any idea about this ?

-ck



             reply	other threads:[~2023-03-23  8:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  8:18 Chaitanya Kulkarni [this message]
2023-03-24 22:34 ` debugfs message during creation of the NVMeOf controller alan.adamson
2023-03-26 23:44   ` Chaitanya Kulkarni
2023-03-26 23:48     ` Chaitanya Kulkarni
2023-03-27  5:27       ` Chaitanya Kulkarni
2023-03-27 17:44         ` [PATCH] nvme: fix error handling in nvme_init_ctrl() Akinobu Mita
2023-03-27 18:23           ` Chaitanya Kulkarni
2023-03-27 22:12           ` alan.adamson
2023-04-25  8:31         ` debugfs message during creation of the NVMeOf controller 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=40baa75e-fdf5-cb73-5fa8-b12d65bce4e7@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=alan.adamson@oracle.com \
    --cc=linux-nvme@lists.infradead.org \
    /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