Bug 216400 - Firmware activation starting AEN processing prevents further AER commands sent to the NVMe controller.
Summary: Firmware activation starting AEN processing prevents further AER commands sen...
Status: NEW
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: NVMe (show other bugs)
Hardware: All Linux
: P1 high
Assignee: IO/NVME Virtual Default Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-23 01:14 UTC by lixingyuan
Modified: 2022-08-23 01:14 UTC (History)
0 users

See Also:
Kernel Version: v5.19
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description lixingyuan 2022-08-23 01:14:50 UTC 
This bug is related to these two commits:


1. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2&id=4c75f877853cfa81b12374a07208e07b077f39b8

These codes will set the controller state to NVME_CTRL_RESETTING while handling the firmware activation staring AEN

2. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2&id=0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d

When submitting a new AER command to the controller, this code checks if the controller state is NVME_CTRL_LIVE. This caused the problem. When the firmware activation staring AEN was processed before, the controller state was already set to NVME_CTRL_RESETTING, which resulted in no new AER commands being sent to the controller.
Note You need to log in before you can comment on or make changes to this bug.