On Tue, Nov 12, 2019 at 10:15:00PM -0500, Martin K. Petersen wrote:
I was able to reproduce the same stack trace with this patchWhile trying to understand what's going on in the Oops below I figured
that it could be the result of the invalid pointer access. The patch
still needs testing by our customer but indepent of this I think the
patch fixes a real bug.
applied... That is obviously bad. The good news, I have access to this
machine, so maybe I able to figure out what's the root cause of this