Re: CFI failure at nfsd4_encode_operation+0xa2/0x210 [nfsd]

[Chuck Lever via Bugspray Bot <bugbot@kernel.org>]

Chuck Lever writes via Kernel.org Bugzilla:

(In reply to Rin Cat from comment #3)
> I no longer had this issue when I moved to LTS 6.6 kernel from LTS 6.1, so I
> am not sure where it was fixed.

If you want to find the specific commit that resolved the issue, the best you can do is bisect between v6.1 and v6.13, applying the flow integrity check at each step. That shouldn't be more than two dozen steps.

I don't think we would have explicitly fixed a flow integrity bug, our current tooling does not point those out.

 
> And for Jeff, CFI (Control Flow Integrity) is LLVM/clang supported runtime
> type check.
> If a pointer or function argument is different or incompatible with the
> declared type, a kernel warning or panic will be triggered depending on the
> configuration.
> 
> https://clang.llvm.org/docs/ControlFlowIntegrity.html
> 
> A CFI failure most likely means some runtime bugs.

If v6.1.127 still triggers a CFI warning, it would help if you could bisect as described above and report the result here.

Are you able to regularly test upstream kernels or even this branch:

https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/log/?h=nfsd-testing

View: https://bugzilla.kernel.org/show_bug.cgi?id=217973#c4
You can reply to this message to join the discussion.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)