nvmet: Fix discover log page when offsets are used
Subsystems (2)
PATCH v2 1/1 nvmet: Fix discover log page when offsets are used
The nvme target hadn't been taking the Get Log Page offset parameter into consideration, and so has been returning corrupted logs pages when offsets are used. Since many tools, including nvme-cli, split the log request to 4k, we've been breaking discovery log responses when more than 3 subsystems exist.
Fix the log page by internally generating the entire discovery log page and copying only the requested bytes into the user buffer.
---
v1 -> v2:
Fixed releasing nvmet_config_sem read lock
Fixed commit log spelling error
Return invalid field if offset is not dword aligned. This is spec optional, but it's either check these bits or mask them off. I just chose the former.
drivers/nvme/target/admin-cmd.c | 10 ++++++ drivers/nvme/target/discovery.c | 68 ++++++++++++++++++++++++++--------------- drivers/nvme/target/nvmet.h | 1 + 3 files changed, 55 insertions(+), 24 deletions(-)
drivers/nvme/target/admin-cmd.c +10 -0
@@ -24,6 +24,16 @@ u32 nvmet_get_log_page_len(struct nvme_command *cmd)return len; } +u64 nvmet_get_log_page_offset (struct nvme_command *cmd) +{ +u64 offset =le32_to_cpu (cmd->get_log_page.lpou); + + offset <<=32 ; + offset +=le32_to_cpu (cmd->get_log_page.lpol); + +return offset; +} +static void nvmet_execute_get_log_page_noop (struct nvmet_req *req) {nvmet_req_complete (req,nvmet_zero_sgl (req,0 , req->data_len));
drivers/nvme/target/discovery.c +44 -24
109 lines not on this page · raw message
drivers/nvme/target/nvmet.h +1 -0
@@ -428,6 +428,7 @@ u16 nvmet_copy_from_sgl(struct nvmet_req *req, off_t off, void *buf,u16 nvmet_zero_sgl (struct nvmet_req *req,off_t off,size_t len);u32 nvmet_get_log_page_len (struct nvme_command *cmd); +u64 nvmet_get_log_page_offset (struct nvme_command *cmd);extern struct list_head *nvmet_ports; void nvmet_port_disc_changed(struct nvmet_port *port,
Signature · 1 line
2.14.4
PATCH v2 1/1 nvmet: Fix discover log page when offsets are used
Quoted 32 lines · Keith Busch
The nvme target hadn't been taking the Get Log Page offset parameter into consideration, and so has been returning corrupted logs pages when offsets are used. Since many tools, including nvme-cli, split the log request to 4k, we've been breaking discovery log responses when more than 3 subsystems exist.
Fix the log page by internally generating the entire discovery log page and copying only the requested bytes into the user buffer.
Cc Hannes Reinecke <hare at suse.de>Signed-off-by Keith Busch <keith.busch at intel.com>---
v1 -> v2:Fixed releasing
nvmet_config_semread lockFixed commit log spelling error
Return invalid field if offset is not dword aligned. This is spec optional, but it's either check these bits or mask them off. I just chose the former.
drivers/nvme/target/admin-cmd.c | 10 ++++++ drivers/nvme/target/discovery.c | 68 ++++++++++++++++++++++++++--------------- drivers/nvme/target/nvmet.h | 1 + 3 files changed, 55 insertions(+), 24 deletions(-)drivers/nvme/target/admin-cmd.c +0
-0
drivers/nvme/target/admin-cmd.c u32 nvmet_get_log_page_len(struct nvme_command *cmd) · line 27
Quoted 4 lines
drivers/nvme/target/admin-cmd.c +0
-0@@ -24,6 +24,16 @@ u32 nvmet_get_log_page_len(struct nvme_command *cmd)return len; }
I didn't see anything this time.
-- james
PATCH v2 1/1 nvmet: Fix discover log page when offsets are used
In reply to Keith BuschThanks for the patch Keith. May we should add a test in blktests for this.
Please see my in-line comments.
Quoted 35 lines · Keith Busch
The nvme target hadn't been taking the Get Log Page offset parameter into consideration, and so has been returning corrupted logs pages when offsets are used. Since many tools, including nvme-cli, split the log request to 4k, we've been breaking discovery log responses when more than 3 subsystems exist.
Fix the log page by internally generating the entire discovery log page and copying only the requested bytes into the user buffer.
Cc Hannes Reinecke <hare at suse.de>Signed-off-by Keith Busch <keith.busch at intel.com>---
v1 -> v2:Fixed releasing
nvmet_config_semread lockFixed commit log spelling error
Return invalid field if offset is not dword aligned. This is spec optional, but it's either check these bits or mask them off. I just chose the former.
drivers/nvme/target/admin-cmd.c | 10 ++++++ drivers/nvme/target/discovery.c | 68 ++++++++++++++++++++++++++--------------- drivers/nvme/target/nvmet.h | 1 + 3 files changed, 55 insertions(+), 24 deletions(-)drivers/nvme/target/admin-cmd.c +0
-0@@ -24,6 +24,16 @@ u32 nvmet_get_log_page_len(struct nvme_command *cmd)return len; }
drivers/nvme/target/admin-cmd.c u32 nvmet_get_log_page_len(struct nvme_command *cmd) · line 36
Quoted 10 lines
drivers/nvme/target/admin-cmd.c +10
-0+u64 nvmet_get_log_page_offset (struct nvme_command *cmd) +{ +u64 offset =le32_to_cpu (cmd->get_log_page.lpou); + + offset <<=32 ; + offset +=le32_to_cpu (cmd->get_log_page.lpol); + +return offset; +} +
Can we please mark above function inline ?
Quoted 18 lines
drivers/nvme/target/admin-cmd.c +0
-0static void nvmet_execute_get_log_page_noop (struct nvmet_req *req) {nvmet_req_complete (req,nvmet_zero_sgl (req,0 , req->data_len));drivers/nvme/target/discovery.c +7
-0@@ -131,54 +131,75 @@ static void nvmet_set_disc_traddr(struct nvmet_req *req, struct nvmet_port *portmemcpy (traddr, port->disc_addr.traddr,NVMF_TRADDR_SIZE ); } +static size_t discovery_log_entries (struct nvmet_req *req) +{ +struct nvmet_ctrl *ctrl = req->sq->ctrl; +struct nvmet_subsys_link *p; +struct nvmet_port *r; +u32 entries =0 ; +
drivers/nvme/target/discovery.c static void nvmet_set_disc_traddr(struct nvmet_req *req, struct nvmet_port *port · line 150
Quoted 10 lines
drivers/nvme/target/discovery.c +10
-0+list_for_each_entry (p, &req->port->subsystems, entry) { +if (!nvmet_host_allowed (p->subsys, ctrl->hostnqn)) +continue ; + entries++; + } +list_for_each_entry (r, &req->port->referrals, entry) + entries++; +return entries; +} +
Return value of the above function has different data type than the variable that we are returning. May we should use the same return data type and the variable data type to avoid warnings from static analysis tools.
Quoted 10 lines
drivers/nvme/target/discovery.c +2
-2static void nvmet_execute_get_disc_log_page (struct nvmet_req *req) {const int entry_size =sizeof (struct nvmf_disc_rsp_page_entry );struct nvmet_ctrl *ctrl = req->sq->ctrl;struct nvmf_disc_rsp_page_hdr *hdr; +u64 offset =nvmet_get_log_page_offset (req->cmd);size_t data_len =nvmet_get_log_page_len (req->cmd); -size_t alloc_len =max (data_len,sizeof (*hdr)); -int residual_len = data_len -sizeof (*hdr); +size_t alloc_len;
drivers/nvme/target/discovery.c static void nvmet_set_disc_traddr(struct nvmet_req *req, struct nvmet_port *port · line 168
Quoted 10 lines
drivers/nvme/target/discovery.c +6
-0struct nvmet_subsys_link *p;struct nvmet_port *r;u32 numrec =0 ;u16 status =0 ; +void *buffer; + +if (offset &0x3 ) { + status =NVME_SC_INVALID_FIELD |NVME_SC_DNR ; + goto out; + }
May be as a comment here with 0x3 to make code more readable?
Quoted 57 lines
drivers/nvme/target/discovery.c +17
-19/* * Make sure we're passing at least a buffer of response header size. * If host provided data len is less than the header size, only the * number of bytes requested by host will be sent to host. */ - hdr =kzalloc (alloc_len,GFP_KERNEL ); -if (!hdr) { +down_read (&nvmet_config_sem); + alloc_len =sizeof (*hdr) + entry_size *discovery_log_entries (req); + buffer =kzalloc (alloc_len,GFP_KERNEL ); +if (!buffer) { +up_read (&nvmet_config_sem); status =NVME_SC_INTERNAL ; goto out; } -down_read (&nvmet_config_sem); + hdr = buffer;list_for_each_entry (p, &req->port->subsystems, entry) { +char traddr[NVMF_TRADDR_SIZE ]; +if (!nvmet_host_allowed (p->subsys, ctrl->hostnqn))continue ; -if (residual_len >= entry_size) { -char traddr[NVMF_TRADDR_SIZE ]; - -nvmet_set_disc_traddr (req, req->port, traddr); -nvmet_format_discovery_entry (hdr, req->port, - p->subsys->subsysnqn, traddr, -NVME_NQN_NVME , numrec); - residual_len -= entry_size; - } + +nvmet_set_disc_traddr (req, req->port, traddr); +nvmet_format_discovery_entry (hdr, req->port, + p->subsys->subsysnqn, traddr, +NVME_NQN_NVME , numrec); numrec++; }list_for_each_entry (r, &req->port->referrals, entry) { -if (residual_len >= entry_size) { -nvmet_format_discovery_entry (hdr, r, -NVME_DISC_SUBSYS_NAME , - r->disc_addr.traddr, -NVME_NQN_DISC , numrec); - residual_len -= entry_size; - } +nvmet_format_discovery_entry (hdr, r, +NVME_DISC_SUBSYS_NAME , + r->disc_addr.traddr, +NVME_NQN_DISC , numrec); numrec++; }
drivers/nvme/target/discovery.c static void nvmet_execute_get_disc_log_page(struct nvmet_req *req) · line 190
Quoted 4 lines
drivers/nvme/target/discovery.c +0
-1@@ -187,11 +208,10 @@ static void nvmet_execute_get_disc_log_page(struct nvmet_req *req) hdr->recfmt =cpu_to_le16 (0 );nvmet_clear_aen_bit (req,NVME_AEN_BIT_DISC_CHANGE ); -
any reason we are getting rid of above extra line ?
Quoted 22 lines
drivers/nvme/target/discovery.c +2
-2up_read (&nvmet_config_sem); - status =nvmet_copy_to_sgl (req,0 , hdr, data_len); -kfree (hdr); + status =nvmet_copy_to_sgl (req,0 , buffer + offset, data_len); +kfree (buffer); out:nvmet_req_complete (req, status); }drivers/nvme/target/nvmet.h +1
-0@@ -428,6 +428,7 @@ u16 nvmet_copy_from_sgl(struct nvmet_req *req, off_t off, void *buf,u16 nvmet_zero_sgl (struct nvmet_req *req,off_t off,size_t len);u32 nvmet_get_log_page_len (struct nvme_command *cmd); +u64 nvmet_get_log_page_offset (struct nvme_command *cmd);extern struct list_head *nvmet_ports; void nvmet_port_disc_changed(struct nvmet_port *port,
Christoph Hellwig
maintainerPATCH v2 1/1 nvmet: Fix discover log page when offsets are used
Quoted 11 lines · Chaitanya Kulkarni
drivers/nvme/target/admin-cmd.c u32 nvmet_get_log_page_len(struct nvme_command *cmd) · line 36
Quoted 10 lines
drivers/nvme/target/admin-cmd.c +10
-0+u64 nvmet_get_log_page_offset (struct nvme_command *cmd) +{ +u64 offset =le32_to_cpu (cmd->get_log_page.lpou); + + offset <<=32 ; + offset +=le32_to_cpu (cmd->get_log_page.lpol); + +return offset; +} +Can we please mark above function inline ?
Log pages are pretty much in the slow path, so despite the triviality I don't really see a reason to inline it.
Christoph Hellwig
maintainerPATCH v2 1/1 nvmet: Fix discover log page when offsets are used
In reply to Keith Buschdrivers/nvme/target/admin-cmd.c u32 nvmet_get_log_page_len(struct nvme_command *cmd) · line 34
Quoted 8 lines
drivers/nvme/target/admin-cmd.c +8
-0+u64 nvmet_get_log_page_offset (struct nvme_command *cmd) +{ +u64 offset =le32_to_cpu (cmd->get_log_page.lpou); + + offset <<=32 ; + offset +=le32_to_cpu (cmd->get_log_page.lpol); + +return offset;
Maybe just a pet peeve of fine, but can we avoid the pointless local variable? Why not:
return le32_to_cpu(cmd->get_log_page.lpol) | (((u64)le32_to_cpu(cmd->get_log_page.lpou)) << 32);
That being said I don't get why we don't simply replace lpol and lpou with a single __le64 to start with to simplify things further.
Keith Busch
maintainerPATCH v2 1/1 nvmet: Fix discover log page when offsets are used
Quoted 12 lines · Christoph Hellwig
drivers/nvme/target/admin-cmd.c u32 nvmet_get_log_page_len(struct nvme_command *cmd) · line 34
Quoted 8 lines
drivers/nvme/target/admin-cmd.c +8
-0+u64 nvmet_get_log_page_offset (struct nvme_command *cmd) +{ +u64 offset =le32_to_cpu (cmd->get_log_page.lpou); + + offset <<=32 ; + offset +=le32_to_cpu (cmd->get_log_page.lpol); + +return offset;Maybe just a pet peeve of fine, but can we avoid the pointless local variable? Why not:
Quoted 2 lines
return le32_to_cpu(cmd->get_log_page.lpol) | (((u64)le32_to_cpu(cmd->get_log_page.lpou)) << 32);
Sure thing.
Quoted 2 lines
That being said I don't get why we don't simply replace lpol and lpou with a single
__le64to start with to simplify things further.
It is on a natrual 8 byte alignment, so I guess we could make it an __le64. The split just aligns to the spec.
PATCH v2 1/1 nvmet: Fix discover log page when offsets are used
Quoted 16 lines · Keith Busch
Quoted 12 lines · Christoph Hellwig
drivers/nvme/target/admin-cmd.c u32 nvmet_get_log_page_len(struct nvme_command *cmd) · line 34
Quoted 8 lines
drivers/nvme/target/admin-cmd.c +8
-0+u64 nvmet_get_log_page_offset (struct nvme_command *cmd) +{ +u64 offset =le32_to_cpu (cmd->get_log_page.lpou); + + offset <<=32 ; + offset +=le32_to_cpu (cmd->get_log_page.lpol); + +return offset;Maybe just a pet peeve of fine, but can we avoid the pointless local variable? Why not:
Quoted 2 lines
return le32_to_cpu(cmd->get_log_page.lpol) | (((u64)le32_to_cpu(cmd->get_log_page.lpou)) << 32);
Quoted 7 lines
Sure thing.
Quoted 2 lines
That being said I don't get why we don't simply replace lpol and lpou with a single
__le64to start with to simplify things further.It is on a natrual 8 byte alignment, so I guess we could make it an
__le64. The split just aligns to the spec.
How about introducing a union such that the names from the spec can be retained and at the same time nvmet_get_log_page_offset() can read a single __le64 variable?
Bart.