| |||||||||||||
A kernel change breaks GlusterFSA kernel change breaks GlusterFSPosted Mar 28, 2013 17:54 UTC (Thu) by jimparis (subscriber, #38647)In reply to: A kernel change breaks GlusterFS by mkerrisk Parent article: A kernel change breaks GlusterFS
> The question is where you consider the definition of the ABI to be. Is it some documented standard ("this is a 64-bit field"), or is it "the behavior as (it appears to be) implemented" ("only 32 bits are ever used in this field")? The GlusterFS folks clearly took it to be the latter. One can argue that it was a questionable decision, but given the problem they were trying to solve, and the constraints on how much information they could pass in the cookie sent over NFSv3, it wasn't a completely insane thing to do, given the observed kernel behavior.
There are two things they could have done that would have made it less insane:
- Ask the kernel developers if it's OK to assume high bits are zero
- Verify the assumption with an assert (instead of missing files and going into infinite loops)
(Log in to post comments)
|
|||||||||||||