Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nvme-print-binary: add effects-log command output missed #2409

Merged
merged 1 commit into from
Jul 10, 2024

Conversation

ikegami-t
Copy link
Contributor

The csi data added before effects log page output.

The csi data added before effects log page output.

Signed-off-by: Tokunori Ikegami <[email protected]>
@ikegami-t
Copy link
Contributor Author

Fix for the isseu #2405.

@igaw
Copy link
Collaborator

igaw commented Jul 10, 2024

The 1.16 code base only prints the effects log in binary mode. Is this something we should/need to keep?

@ikegami-t
Copy link
Contributor Author

The effects log was changed by 155fbeb to add CSI but looks not applied the changes in the 1.16 code. So currently multiple CSIs effects logs are output then if not added the CSI data then seems difficult to know which CSI effects log from the binary output. But still should we keep the output before?

@igaw
Copy link
Collaborator

igaw commented Jul 10, 2024

I suppose the main use case is to store it into a file and do some operation on it. I was wondering if we mix different section into the output it makes it hard to use. But the CSI section and the effect section have a fixed size.

Alright, let's go with this.

@igaw igaw merged commit 5746db3 into linux-nvme:master Jul 10, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants