From: Dave Hansen <dave.hansen@intel.com>
To: "Habil Eren Türker" <habilerenturker@hotmail.com>
Cc: "bp@alien8.de" <bp@alien8.de>,
"daniel@quora.org" <daniel@quora.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"jwiesner@suse.de" <jwiesner@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] x86/hpet: Mark boot-time variables as __ro_after_init
Date: Thu, 19 Nov 2026 14:44:15 -0800 [thread overview]
Message-ID: <19fd45ea-4566-43d1-aee0-6d22c8026f79@intel.com> (raw)
In-Reply-To: <20261119203747.80853-1-habilerenturker@hotmail.com>
On 11/19/26 12:37, Habil Eren Türker wrote:
> Marking these as __ro_after_init hardens the kernel by placing them in the
> read-only data section post-init. This prevents accidental or malicious
> runtime modifications (e.g., via a memory corruption exploit) that could
> silently corrupt HPET frequencies or block IDs, causing severe timing
> issues or system hangs.
Heh, I'm familiar with the concept of __ro_after_init.
Maybe it's a sign of the times, but I'm doubting the veracity of the
claim that this was found through a random human audit of the HPET code.
I mean, if you're using an LLM to find these, generate the patches, and
respond to my emails, that *fine*. Just please be transparent about it
when I ask.
next prev parent reply other threads:[~2026-11-19 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 12:29 Habil Eren Türker
2026-11-19 19:40 ` Dave Hansen
2026-11-19 20:37 ` Habil Eren Türker
2026-11-19 22:44 ` Dave Hansen [this message]
2026-11-19 23:02 ` Habil Eren Türker
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=19fd45ea-4566-43d1-aee0-6d22c8026f79@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=daniel@quora.org \
--cc=dave.hansen@linux.intel.com \
--cc=habilerenturker@hotmail.com \
--cc=hpa@zytor.com \
--cc=jwiesner@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®