From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <kch@nvidia.com>, linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
dlemoal@kernel.org, bvanassche@acm.org
Subject: Re: [PATCH V2] nvmet: fix compilation errors
Date: Wed, 15 Jan 2025 15:33:59 -0700 [thread overview]
Message-ID: <8901cba4-245b-4b02-832b-af02e5bb9cb8@kernel.dk> (raw)
In-Reply-To: <20250115221703.62861-1-kch@nvidia.com>
On 1/15/25 3:17 PM, Chaitanya Kulkarni wrote:
> nvmet_alloc_ctrl() only takes nvmet_alloc_ctrl_args. nvmet_alloc_ctrl
> doesn't have nvmet_req argument. In nvmet_alloc_ctrl nvmet_req is
> needed when setting up authentication capabilities since call to
> nvmet_setup_auth() requires nvmet_req argument which later uses req->sq
> to determnine if tls is enabled or not.
>
> That leads to following compilation errors:-
>
> target/fabrics-cmd.c: In function ?nvmet_execute_admin_connect?:
> target/fabrics-cmd.c:318:35: error: too few arguments to function ?nvmet_connect_result?
> | ^~~~~~~~~~~
> target/fabrics-cmd.c:237:12: note: declared here
> 237 | static u32 nvmet_connect_result(struct nvmet_ctrl *ctrl, struct nvmet_req *req)
> | ^~~~~~~~~~~~~~~~~~~~
> make[4]: *** [/mnt/data/nvme/scripts/Makefile.build:194: target/fabrics-cmd.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> target/core.c: In function ?nvmet_alloc_ctrl?:
> target/core.c:1527:37: error: ?struct nvmet_alloc_ctrl_args? has no member named ?req?
> 1527 | struct nvmet_req *req = args->req;
> | ^~
> target/core.c:1635:25: error: too few arguments to function ?nvmet_setup_auth?
> 1635 | dhchap_status = nvmet_setup_auth(ctrl);
> | ^~~~~~~~~~~~~~~~
> In file included from target/trace.h:19,
> from target/core.c:16:
> target/nvmet.h:879:4: note: declared here
> 879 | u8 nvmet_setup_auth(struct nvmet_ctrl *ctrl, struct nvmet_req *req);
> | ^~~~~~~~~~~~~~~~
> target/core.c:1654:17: error: too few arguments to function ?nvmet_has_auth?
> 1654 | nvmet_has_auth(ctrl) ? " with DH-HMAC-CHAP" : "");
> | ^~~~~~~~~~~~~~
> 889 | static inline bool nvmet_has_auth(struct nvmet_ctrl *ctrl, struct nvmet_req *req)
> | ^~~~~~~~~~~~~~
> target/core.c:1527:27: warning: unused variable ?req? [-Wunused-variable]
> 1527 | struct nvmet_req *req = args->req;
> | ^~~
>
> Fix these errors with addition of the nvmet_req *req parameter to
> nvmet_alloc_ctrl(), new prototype :-
I think that "what tree is this" applies to this as a whole. None of
this seems to make sense looking at my for-next tree...
--
Jens Axboe
prev parent reply other threads:[~2025-01-15 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 22:17 [PATCH V2] nvmet: fix compilation errors Chaitanya Kulkarni
2025-01-15 22:22 ` Jens Axboe
2025-01-15 22:33 ` Keith Busch
2025-01-15 22:34 ` Jens Axboe
2025-01-16 1:16 ` Chaitanya Kulkarni
2025-01-16 1:56 ` Jens Axboe
2025-01-16 1:15 ` Chaitanya Kulkarni
2025-01-15 22:33 ` Jens Axboe [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=8901cba4-245b-4b02-832b-af02e5bb9cb8@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@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