From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Jannik Glückert" <jannik.glueckert@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Huang Rui <ray.huang@amd.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Power Management <linux-pm@vger.kernel.org>,
Linux LLVM Build Support <llvm@lists.linux.dev>
Subject: Re: Fwd: CFI violation when reading amd_pstate/status
Date: Mon, 7 Aug 2023 08:39:53 +0200 [thread overview]
Message-ID: <2023080747-outsider-despite-acd2@gregkh> (raw)
In-Reply-To: <CAFqe=zJ9uRTVG=jny2PzUrrFGW2E_mZrGKF-3YMRkjzMUdu_7A@mail.gmail.com>
On Mon, Aug 07, 2023 at 08:21:37AM +0200, Jannik Glückert wrote:
> Hi Greg,
>
> our kernel uses the Fedora config and has a homeopathic patchset on
> top of upstream - see
> https://gitweb.gentoo.org/proj/linux-patches.git/tree/?h=6.4 except
> the 50** patches.
> Namely we don't touch cpufreq or pm.
>
> > Comm: cat Tainted: P
>
> I am not using any out of tree modules, the kernel switches to
> Tainted: P on the first CFI violation.
Ah, ok. Then work with the amd_pstate driver authors on this, odds are
one of the sysfs callbacks is incorrectly created which is quite easy to
do for stuff like this. CFI also gets confused at times when dealing
with sysfs attributes due to them being cast in all sorts of crazy ways.
good luck!
greg k-h
next prev parent reply other threads:[~2023-08-07 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 23:55 Fwd: CFI violation when reading amd_pstate/status Bagas Sanjaya
2023-08-07 6:03 ` Greg Kroah-Hartman
2023-08-07 6:21 ` Jannik Glückert
2023-08-07 6:39 ` Greg Kroah-Hartman [this message]
2023-08-07 16:15 ` Nick Desaulniers
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=2023080747-outsider-despite-acd2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=jannik.glueckert@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ray.huang@amd.com \
/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