common/frag: properly convert frag_t to net/store endianness#66199
common/frag: properly convert frag_t to net/store endianness#66199
Conversation
OK, so just for clarity -- this isn't the issue that causes BE kclient hosts to loop on readdir, right? Its a fix for MDSs running on BE architectures. |
Correct, I do not believe at this time that this is the cause.
Yes. |
|
This patch can be used for some basic validation: which lets us see: Unfortunately this needs printed to |
|
Did you audit our other uses of encode_raw? |
Yes, there are others. Notably
It has been that way since the beginning of the git history (~2007). |
|
@batrick - not sure about this , so asking -- do we need to do a PSA to our community users regarding this issue? |
Can't hurt. I'll write one up. |
|
This PR is under test in https://tracker.ceph.com/issues/73938. |
|
Need to retest with https://tracker.ceph.com/issues/74026 |
e6deca3 to
b1bdc63
Compare
* refs/pull/66199/head: Reviewed-by: Venky Shankar <vshankar@redhat.com>
Of particular interest is the CPU architecture and endianness. Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
The MDS/client are already accidentally doing the right thing unless they are running on a big-endian machine. Credit to Venky Shankar for originally hypothesizing an endianness issue with the frag_t. Fixes: https://tracker.ceph.com/issues/73792 Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
There's better tooling for this now and we can avoid magic numbers. Fixes: https://tracker.ceph.com/issues/73792 Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
If a big-endian MDS writes frag_t values into the metadata pool, these will persist and confuse the MDS after it tries properly parsing them as little-endian. Fortunately detecting this situation is fairly easy as we restrict the number of bits and the number of bits restricts the mask value. Fixes: https://tracker.ceph.com/issues/73792 Signed-off-by: Patrick Donnelly <pdonnell@ibm.com>
|
jenkins test api |
|
@vshankar I've resolved the |
The MDS/client are already accidentally doing the right thing unless they are running on a big-endian machine.
Fixes: https://tracker.ceph.com/issues/73792
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
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job DefinitionYou must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.