public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Rin Cat via Bugspray Bot <bugbot@kernel.org>
To: linux-nfs@vger.kernel.org, jlayton@kernel.org, anna@kernel.org,
	 trondmy@kernel.org, cel@kernel.org
Subject: Re: CFI failure at nfsd4_encode_operation+0xa2/0x210 [nfsd]
Date: Fri, 31 Jan 2025 20:15:07 +0000	[thread overview]
Message-ID: <20250131-b217973c3-c25737af37f7@bugzilla.kernel.org> (raw)
In-Reply-To: <20250131-b217973c0-a2ac608a1bf9@bugzilla.kernel.org>

Rin Cat writes via Kernel.org Bugzilla:

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.

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.

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


  parent reply	other threads:[~2025-01-31 20:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 15:15 CFI failure at nfsd4_encode_operation+0xa2/0x210 [nfsd] Rin Cat via Bugspray Bot
2025-01-31 15:15 ` Chuck Lever via Bugspray Bot
2025-01-31 19:00 ` Jeff Layton via Bugspray Bot
2025-01-31 20:15 ` Rin Cat via Bugspray Bot [this message]
2025-01-31 21:00   ` Chuck Lever via Bugspray Bot
2025-01-31 21:05 ` Rin Cat via Bugspray Bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250131-b217973c3-c25737af37f7@bugzilla.kernel.org \
    --to=bugbot@kernel.org \
    --cc=anna@kernel.org \
    --cc=cel@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox