On 15/11/15 16:38, James Ralston wrote:
On Sun, Nov 15, 2015 at 4:22 PM, Simo Sorce <simo(a)redhat.com>
wrote:
> Long story short there is a kernel bug that triggers this, we have
> patches for both the kernel and a wrokaround for gssproxy that
> should deal with this.
If you can point me to the workaround patches for gssproxy, I'll roll
a local gssproxy RPM with the patches to see if that addresses our
problem.
Patches were release with 0.4.0.
> Can you tell me also what kernel and gssproxy version do you have
?
$ repoquery --envra --installed gssproxy kernel
0:gssproxy-0.3.0-10.el7.x86_64
0:kernel-3.10.0-123.el7.x86_64
0:kernel-3.10.0-229.14.1.el7.x86_64
0:kernel-3.10.0-229.20.1.el7.x86_64
$ uname -r
3.10.0-229.20.1.el7.x86_64
Btw if you are a RH customer open a case and we can help you with an
hotfix until the packages is released for general availability (real
soon now anyway I think).
Simo.
--
Simo Sorce * Red Hat, Inc * New York