nvme: clear the prp2 field of the nvme command.
PATCH 1/1 nvme: clear the prp2 field of the nvme command.
If the prp2 field is not filled in nvme_setup_prp_simple(), the prp2 field is garbage data. According to nvme spec, the prp2 is reserved if the data transfer does not cross a memory page boundary. Writing a reserved coded value into a controller property field produces undefined results, so it needs to be cleared in nvme_setup_rw().
--- drivers/nvme/host/core.c | 1 + 1 file changed, 1 insertion(+)
drivers/nvme/host/core.c +1 -0
@@ -891,6 +891,7 @@ static inline blk_status_t nvme_setup_rw(struct nvme_ns *ns, cmnd->rw.reftag =0 ; cmnd->rw.apptag =0 ; cmnd->rw.appmask =0 ; + cmnd->rw.dptr.prp2 =0 ;if (ns->ms) {/*
Signature · 1 line
2.34.1
Quoted 7 lines · Lei Rao
If the prp2 field is not filled in
nvme_setup_prp_simple(), the prp2 field is garbage data. According to nvme spec, the prp2 is reserved if the data transfer does not cross a memory page boundary. Writing a reserved coded value into a controller property field produces undefined results, so it needs to be cleared innvme_setup_rw().Signed-off-by Lei Rao <[email protected]>
if it is reserved then controller shoule ignore this field, no ?
not sure if original author wanted to avoid an extra assignment in the fast path with assumption that reserved fields should be ignored if it is then we should avoid this, if not then looks good
-ck
Quoted 10 lines · Chaitanya Kulkarni
Quoted 7 lines · Lei Rao
If the prp2 field is not filled in
nvme_setup_prp_simple(), the prp2 field is garbage data. According to nvme spec, the prp2 is reserved if the data transfer does not cross a memory page boundary. Writing a reserved coded value into a controller property field produces undefined results, so it needs to be cleared innvme_setup_rw().Signed-off-by Lei Rao <[email protected]>if it is reserved then controller shoule ignore this field, no ?
It's feasible for the controller to ignore this field. But our controller has stricter checks, and if prp2 is not used but has a value, some warnings will be printed. According to the NVMe spec, it seems to write a reserved field produces an undefined result, so maybe clearing it is better.
Thanks,
Lei
Quoted 9 lines
not sure if original author wanted to avoid an extra assignment in the fast path with assumption that reserved fields should be ignored if it is then we should avoid this, if not then looks good
Reviewed-by Chaitanya Kulkarni <[email protected]>-ck
[email protected]
maintainerQuoted 3 lines · Lei
stricter checks, and if prp2 is not used but has a value, some warnings will be printed. According to the NVMe spec, it seems to write a reserved field produces an undefined result, so maybe clearing it is better.
NVMe is a little weird about reserved fields settable by the host. I don't think your controllers warnings are correct, but given that the cost of clearing is very low I think we should clear it in Linux. Please resend a patch with the clearing in the right place as suggested in my previous mail.
Christoph Hellwig
maintainerQuoted 5 lines · Lei Rao
If the prp2 field is not filled in
nvme_setup_prp_simple(), the prp2 field is garbage data. According to nvme spec, the prp2 is reserved if the data transfer does not cross a memory page boundary. Writing a reserved coded value into a controller property field produces undefined results, so it needs to be cleared innvme_setup_rw().
But this is not the right place to clear it, that needs to be done in the place that sets up the PRPs, і.e. nvme_setup_prp_simple.