Skip to content

Comments

mds: enforce usage of host error in cephfs, use errorcode32_t in MClientReply message#60286

Merged
salieri11 merged 5 commits intoceph:mainfrom
salieri11:igolikov-wip-bug-64611
Feb 19, 2025
Merged

mds: enforce usage of host error in cephfs, use errorcode32_t in MClientReply message#60286
salieri11 merged 5 commits intoceph:mainfrom
salieri11:igolikov-wip-bug-64611

Conversation

@salieri11
Copy link
Contributor

Use errorcode32_t struct in MClientReply message

  • This struct enforces converting error code from host to ceph and back, while encoding and decoding messages, respectelvly.

Enforce usage of E* error codes in the cephfs code instead of CEPHFS_E* error codes

  • cephfs code now use host error codes instead of CEPHFS_* error codes

Fixes https://tracker.ceph.com/issues/64611

Contribution Guidelines

  • To sign and title your commits, please refer to Submitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands
  • jenkins retest this please
  • jenkins test classic perf
  • jenkins test crimson perf
  • jenkins test signed
  • jenkins test make check
  • jenkins test make check arm64
  • jenkins test submodules
  • jenkins test dashboard
  • jenkins test dashboard cephadm
  • jenkins test api
  • jenkins test docs
  • jenkins render docs
  • jenkins test ceph-volume all
  • jenkins test ceph-volume tox
  • jenkins test windows
  • jenkins test rook e2e

@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from a6637a5 to 7fc4437 Compare October 13, 2024 16:28
@salieri11 salieri11 changed the title enforce usage of errorcode_32t in cephhfs mds: enforce usage of host error in cephhfs, use errorcode32_t in MClientReply message Oct 13, 2024
@salieri11
Copy link
Contributor Author

jenkins test make check

@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from 7fc4437 to a57df10 Compare October 14, 2024 10:14
@vshankar vshankar requested a review from a team October 14, 2024 15:59
@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from 2cfc3fe to bee80a4 Compare October 14, 2024 18:40
@salieri11
Copy link
Contributor Author

jenkins test make check arm64

@dparmar18
Copy link
Contributor

(just an extreme nit) s/cephhfs/cephfs in the commit title

@salieri11 salieri11 changed the title mds: enforce usage of host error in cephhfs, use errorcode32_t in MClientReply message mds: enforce usage of host error in cephfs, use errorcode32_t in MClientReply message Oct 15, 2024
@github-actions
Copy link

This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved

@salieri11
Copy link
Contributor Author

jenkins test make check

1 similar comment
@salieri11
Copy link
Contributor Author

jenkins test make check

@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from 76d7f55 to 311f62b Compare October 29, 2024 09:03
@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch 3 times, most recently from 9d6291b to c967986 Compare November 1, 2024 16:36
@github-actions
Copy link

github-actions bot commented Nov 4, 2024

This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved

@dparmar18
Copy link
Contributor

LGTM, just need the above two comments to be addressed.

@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from fcbf45c to 3848992 Compare February 5, 2025 09:32
Copy link
Member

@batrick batrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please annotate the commit message which fixes/resolves a Ceph tracker issue with:

Fixes: http://tracker.ceph.com/issues/...

This is essential when examining the history of the repository (this commit fixes what) and helps merge scripts identify issues that have been resolved by a merge. See this article on GitHub on how to amend commits and update your pull request.

Copy link
Member

@batrick batrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Template saved-reply: Please prefix the title of your commit message with the sub-component you are changing. This is required for your PR to be merged.

See this article on GitHub on how to amend commits and update your pull request.

Specific-comment: Your PR would be best split into multiple commits with fixes by each component. Large commits are hard to navigate/review. I also asked for explanations for some changes in previous reviews to be put into commit messages. I saw you left a github comment but what I would have preferred is that you put that response in the commit message and told me to read it there.

When refactoring large change-sets into multiple commits, use git reset -p and git rebase -i to help you restructure the commits. (If you're not already familiar...)

Copy link
Member

@batrick batrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The rest of the changes look good -- thanks!

@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch 2 times, most recently from 8eabaed to 8f551cb Compare February 12, 2025 09:15
@salieri11
Copy link
Contributor Author

jenkins test make check

@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from 8f551cb to 86a66b0 Compare February 13, 2025 10:16
@salieri11
Copy link
Contributor Author

jenkins test make check

1 similar comment
@salieri11
Copy link
Contributor Author

jenkins test make check

@salieri11 salieri11 requested a review from batrick February 16, 2025 17:45
@ceph ceph deleted a comment from github-actions bot Feb 17, 2025
Copy link
Member

@batrick batrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please rebase + squash mds: fix merge error and release notes: explain that old CEPHFS_EXXX code were removed

release notes,python bindings: add note, change pybindings

split into two commits:

  • PendingReleaseNotes: add note on client/mds error codes
  • pybind/cephfs: switch CEPHFS_E error codes to system

@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from 86a66b0 to 90a3ebb Compare February 18, 2025 11:50
@salieri11 salieri11 force-pushed the igolikov-wip-bug-64611 branch from 90a3ebb to 7055fa5 Compare February 18, 2025 12:48
@salieri11
Copy link
Contributor Author

jenkins test api

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants