From: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
To: k@chaosmail.tech
Cc: alexandre.belloni@bootlin.com, andy@kernel.org,
asahi@lists.linux.dev, atharvatiwarilinuxdev@gmail.com,
bhelgaas@google.com, bp@alien8.de, brgl@kernel.org,
dave.hansen@linux.intel.com, dlechner@baylibre.com,
dmitry.kasatkin@gmail.com, eric.snowberg@oracle.com,
griffin@kroah.com, hansg@kernel.org, hpa@zytor.com,
ilpo.jarvinen@linux.intel.com, j@jannau.net, jarkko@kernel.org,
jic23@kernel.org, jmorris@namei.org, lee@kernel.org,
lenb@kernel.org, linusw@kernel.org, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
linux-rtc@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux@roeck-us.net, mfd@lists.linux.dev, mingo@redhat.com,
neal@gompa.dev, nuno.sa@analog.com, paul@paul-moore.com,
pavel@kernel.org, platform-driver-x86@vger.kernel.org,
rafael@kernel.org, roberto.sassu@huawei.com, serge@hallyn.com,
sre@kernel.org, sven@kernel.org, tglx@kernel.org,
wim@linux-watchdog.org, x86@kernel.org, zohar@linux.ibm.com
Subject: Re: [RFC PATCH 14/14] mfd/macsmc: add ioctl to access smc keys
Date: Thu, 29 Oct 2026 10:39:26 -0400 [thread overview]
Message-ID: <20261029143926.1246-1-atharvatiwarilinuxdev@gmail.com> (raw)
In-Reply-To: <525E5B4D-A947-4567-9FCD-5FFF2CA8B161@chaosmail.tech>
> This should either be dropped from the series, or be hidden behind a
> `melt_my_mac`-style module flag, or switched to a whitelist approach.
> We do not know what keys will be introduced in new smc firmware
> versions, and there are already keys that should not be randomly poked
> at.
1. The patch is required, atleast on intel macs, as without writing GPU and CPU
states to smc, the system gives PROCHOT signal under small load
, and heats up a lot.
2. the smc dosent expose keys of nature that can physically damage the system
it only exposes power/volt data, and the most you can poke is reboot
keys and gpu/cpu p-states.
3. If a person is randomly touching keys, Its their problem and not ours.
4. There are a lot of things that can mess the system way more and permanently
than smc (undervolting for example), but they are not safe guarded, why
should this be then?
next prev parent reply other threads:[~2026-10-29 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261029085504.3547-1-atharvatiwarilinuxdev@gmail.com>
[not found] ` <20261029085504.3547-15-atharvatiwarilinuxdev@gmail.com>
2026-10-29 9:22 ` [RFC PATCH 14/14] mfd/macsmc: add ioctl to access smc keys Sasha Finkelstein
2026-10-29 14:39 ` Atharva Tiwari [this message]
2026-10-29 14:53 ` Sasha Finkelstein
2026-10-29 15:25 ` Aditya Garg
2026-10-29 15:42 ` Sasha Finkelstein
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=20261029143926.1246-1-atharvatiwarilinuxdev@gmail.com \
--to=atharvatiwarilinuxdev@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=brgl@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=dlechner@baylibre.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=griffin@kroah.com \
--cc=hansg@kernel.org \
--cc=hpa@zytor.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=j@jannau.net \
--cc=jarkko@kernel.org \
--cc=jic23@kernel.org \
--cc=jmorris@namei.org \
--cc=k@chaosmail.tech \
--cc=lee@kernel.org \
--cc=lenb@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mfd@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=neal@gompa.dev \
--cc=nuno.sa@analog.com \
--cc=paul@paul-moore.com \
--cc=pavel@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=sven@kernel.org \
--cc=tglx@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=x86@kernel.org \
--cc=zohar@linux.ibm.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