On 2/2/2018 6:04 PM, Kodiak Firesmith wrote: > I'm relatively new to handling OpenAFS. Are these problems part of a > normal "kernel release; openafs update" cycle and perhaps I'm getting > snagged just by being too early of an adopter? I wanted to raise the > alarm on this and see if anything else was needed from me as the > reporter of the issue, but perhaps that's an overreaction to what is > just part of a normal process I just haven't been tuned into in prior > RHEL release cycles?
Kodiak,
On RHEL, DKMS is safe to use for kernel modules that restrict themselves
to using the restricted set of kernel interfaces (the RHEL KABI) that
Red Hat has designated will be supported across the lifespan of the RHEL
major version number. OpenAFS is not such a kernel module. As a result
it is vulnerable to breakage each and every time a new kernel is shipped.
There are two types of failures that can occur:
1. a change results in failure to build the OpenAFS kernel module
for the new kernel
2. a change results in the OpenAFS kernel module building and
successfully loading but failing to operate correctly
It is the second of these possibilities that has taken place with the
release of the 3.10.0-830.el7 kernel shipped as part of the RHEL 7.5 beta.
Are you an early adopter of RHEL 7.5 beta? Absolutely, its a beta
release and as such you should expect that there will be bugs and that
third party kernel modules that do not adhere to the KABI functionality
might have compatibility issues.
There was a compatibility issue with RHEL 7.4 kernel
(3.10.0_693.1.1.el7) as well that was only fixed in the OpenAFS 1.6
release series this past week as part of 1.6.22.2:
http://www.openafs.org/dl/openafs/1.6.22.2/RELNOTES-1.6.22.2
Jeffrey Altman
AuriStor, Inc.
P.S. - Welcome to the community.
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
