Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "hare@suse.de" <hare@suse.de>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Subject: Re: [PATCH] nvme-auth: use IS_REACHABLE for nvme_auth_extract_key() declaration
Date: Mon, 3 Nov 2025 19:43:15 +0000	[thread overview]
Message-ID: <53b8bae9-03d5-489a-a9f0-e9323bd0252f@nvidia.com> (raw)
In-Reply-To: <20251103114621.GB15280@lst.de>

On 11/3/25 3:46 AM, Christoph Hellwig wrote:
> So with Keith' latest fixes the auth code should always be built
> in if either the host or target code is built in.  Did this not
> work, or is this for an older branch?
>
>
it errors out with following since NVMe over Fabrics In-Band Authentication
is built-in only on my machine :-

make menuconfig -->  NVMe over Fabrics In-Band Authentication --> *
(* only option no <M>)

nvme (nvme-6.19) # grep NVME_AUTH .config
CONFIG_NVME_AUTH_STATE=y
CONFIG_NVME_AUTH=m
nvme (nvme-6.19) #

Makefile compiles auth.c
   obj-$(CONFIG_NVME_AUTH) += nvme-auth.o
   nvme-auth-y += auth.o
   auth.c gets compiled as part of nvme-auth.ko module
   make[1]: Entering directory '/mnt/data/nvme/drivers/nvme'
   CC [M]  common/auth.o
   CC [M]  host/core.o
   CC [M]  host/sysfs.o
   CC [M]  target/configfs.o
   CC [M]  host/auth.o
   CC [M]  host/fabrics.o
   CC [M]  target/fabrics-cmd-auth.o
   CC [M]  target/auth.o
common/auth.c:158:13: error: redefinition of ‘nvme_auth_extract_key’
   158 | struct key *nvme_auth_extract_key(struct key *keyring, const u8 *secret,
       |             ^~~~~~~~~~~~~~~~~~~~~

-ck



      parent reply	other threads:[~2025-11-03 19:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-02  3:17 [PATCH] nvme-auth: use IS_REACHABLE for nvme_auth_extract_key() declaration Chaitanya Kulkarni
2025-11-03 11:46 ` Christoph Hellwig
2025-11-03 14:54   ` Keith Busch
2025-11-03 19:46     ` Chaitanya Kulkarni
2025-11-03 20:16       ` Keith Busch
2025-11-03 20:28         ` Chaitanya Kulkarni
2025-11-03 21:12           ` Keith Busch
2025-11-03 19:43   ` Chaitanya Kulkarni [this message]

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=53b8bae9-03d5-489a-a9f0-e9323bd0252f@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=ckulkarnilinux@gmail.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --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