nvme: validate CNTLID
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest2 patches 0 repliesNew
- v22 patches 0 repliesSuperseded
- v12 patches 0 repliesSuperseded
Changes to v1 from the cover letter
- split cntlid validation into a separate helper and moved to nvme_init_subsystem()
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | nvme-multipath: avoid crash on invalid subsystem cntlid enumerationdrivers/ | +1 | 2 replies | |
| 2/2 | nvme: validate cntlid during controller initialisationdrivers/ | +30 | 6 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCHv3 0/2] nvme: validate CNTLID
Hi all,
here are two patches to validate correct CNTLID information. A controller might violate the constrain the each CNTLID has to be unique within a subsystem, which then would cause the host to crash.
So these patches prevent this situation by validate the CNTLID and not use the cntlid as part of the device name.
As usual, comments and reviews are welcome.
Changes to v1:
- split cntlid validation into a separate helper and moved to nvme_init_subsystem()
Changes to v2:
- move nvme_validate_cntlid() into critical section when adding nvme controller to the list as suggested by hch
Hannes Reinecke (2):
nvme-multipath: avoid crash on invalid subsystem cntlid enumeration
nvme: validate cntlid during controller initialisation
drivers/nvme/host/core.c | 32 ++++++++++++++++++++++++++++++-- drivers/nvme/host/multipath.c | 2 +- 2 files changed, 31 insertions(+), 3 deletions(-)
Signature · 1 line
2.16.4