Rocksolid Light

News from da outaworlds

mail  files  register  groups  login

Message-ID:  

The smallest worm will turn being trodden on. -- William Shakespeare, "Henry VI"

comp / comp.os.linux.advocacy / Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change

SubjectAuthor
* Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code changerbowman
+* Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code chanvallor
|`- Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code chanrbowman
`* Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code chanChris Ahlstrom
 `- Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code chanvallor

1
Subject: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change
From: rbowman
Newsgroups: comp.os.linux.advocacy
Date: Wed, 15 Jan 2025 01:04 UTC
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: bowman@montana.com (rbowman)
Newsgroups: comp.os.linux.advocacy
Subject: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft
code change
Date: 15 Jan 2025 01:04:32 GMT
Lines: 4
Message-ID: <luofsuF6gdtU3@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 1snKyKKKmWXjKM1y3L80mw5DtJEOprYIZ4WTF22k0TOuKtqB4l
Cancel-Lock: sha1:27NV9TgZY37UCi31fCs3bGkN5DM= sha256:3oQUlIf6Y9YmEhqE+GKp1ph7xrFRzuirPBMFSm5yiYg=
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
View all headers

https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/

We're only here to help... The good news is when vallor, with his thing
about kernels, builds 6.13 it won't blow up.

Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change
From: vallor
Newsgroups: comp.os.linux.advocacy
Date: Wed, 15 Jan 2025 01:47 UTC
References: 1
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: vallor@cultnix.org (vallor)
Newsgroups: comp.os.linux.advocacy
Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy
Microsoft code change
Date: 15 Jan 2025 01:47:33 GMT
Lines: 19
Message-ID: <luoidlF6geaU4@mid.individual.net>
References: <luofsuF6gdtU3@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net Yiax+M5toBYWupTSQFr+ugdLjG1fs1gmzsOnpbQOx/foI94m/D
Cancel-Lock: sha1:Ad6Qwa7fV9OKGoLrJ5sKP5ABLm4= sha256:iVhZ2JwBYchbM+gYMvrP4B61YIXZtWhJTErJvhGiZxE=
X-Face: +McU)#<-H?9lTb(Th!zR`EpVrp<0)1p5CmPu.kOscy8LRp_\u`:tW;dxPo./(fCl
CaKku`)]}.V/"6rISCIDP`
User-Agent: Pan/0.161 (Hmm2; c45f6052; Linux-6.13.0-rc7)
View all headers

On 15 Jan 2025 01:04:32 GMT, rbowman <bowman@montana.com> wrote in
<luofsuF6gdtU3@mid.individual.net>:

> https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
>
> We're only here to help... The good news is when vallor, with his thing
> about kernels, builds 6.13 it won't blow up.

And I booted the latest rc kernel just yesterday. I guess I'm
running the dodgy Microsoft code(!).

Pardon me, while I go boot the release Linux, 6.12.9. (Incidentally,
I've noticed Fedora stays one release behind the current
release -- is that on purpose?)

--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
OS: Linux 6.13.0-rc7 Release: Mint 21.3 Mem: 258G
"Tumbleweed: Colorado Tribble."

Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change
From: rbowman
Newsgroups: comp.os.linux.advocacy
Date: Wed, 15 Jan 2025 06:13 UTC
References: 1 2
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: bowman@montana.com (rbowman)
Newsgroups: comp.os.linux.advocacy
Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy
Microsoft code change
Date: 15 Jan 2025 06:13:18 GMT
Lines: 20
Message-ID: <lup1vuF9kqgU2@mid.individual.net>
References: <luofsuF6gdtU3@mid.individual.net>
<luoidlF6geaU4@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net GDddqxPj5Qfu0n0oHQqRbg7FhvRFJKKWKtvq4aixDx6TmWjJAE
Cancel-Lock: sha1:ZQLjnUpvj7/9OYIQ2rGvs1nECUM= sha256:wGokNJEJLy0M62AySlPk0w9TM2kLhn5t0uzKH5B1GJE=
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
View all headers

On 15 Jan 2025 01:47:33 GMT, vallor wrote:

> On 15 Jan 2025 01:04:32 GMT, rbowman <bowman@montana.com> wrote in
> <luofsuF6gdtU3@mid.individual.net>:
>
>> https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
>>
>> We're only here to help... The good news is when vallor, with his
>> thing about kernels, builds 6.13 it won't blow up.
>
> And I booted the latest rc kernel just yesterday. I guess I'm running
> the dodgy Microsoft code(!).
>
> Pardon me, while I go boot the release Linux, 6.12.9. (Incidentally,
> I've noticed Fedora stays one release behind the current release -- is
> that on purpose?)

I just got 6.12.9 with the dnf update about an hour ago. I don't know if
there is a method in their madness. I took the Ubuntu box up to 24.04 last
week and it's still 6.8.0. It works.

Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change
From: Chris Ahlstrom
Newsgroups: comp.os.linux.advocacy
Organization: None
Date: Wed, 15 Jan 2025 13:13 UTC
References: 1
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: OFeem1987@teleworm.us (Chris Ahlstrom)
Newsgroups: comp.os.linux.advocacy
Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy
Microsoft code change
Date: Wed, 15 Jan 2025 08:13:35 -0500
Organization: None
Lines: 11
Message-ID: <vm8ca0$2ur3p$7@dont-email.me>
References: <luofsuF6gdtU3@mid.individual.net>
Reply-To: OFeem1987@teleworm.us
Injection-Date: Wed, 15 Jan 2025 14:13:36 +0100 (CET)
Injection-Info: dont-email.me; posting-host="d53cf1456c678f3f671de4efd82bba10";
logging-data="3107961"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/KF5SWNWiXz+9RVCC0JbR9"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:AWZGs1NFRFQc3lDFqWUzzsWbWxw=
X-Slrn: Why use anything else?
X-Face: 63n<76,LYJQ2m#'5YL#.T95xqyPiG`ffIP70tN+j"(&@6(4l\7uL)2+/-r0)/9SjZ`qw=
Njn mr93Xrerx}aQG-Ap5IHn"xe;`5:pp"$RH>Kx_ngWw%c\+6qSg!q"41n2[.N/;Pu6q8?+Poz~e
A9? $6_R7cm.l!s8]yfv7x+-FYQ|/k
X-Mutt: The most widely-used MUA
X-User-Agent: Microsoft Outl00k, Usenet K00k Editions
View all headers

rbowman wrote this post while blinking in Morse code:

> https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
>
> We're only here to help... The good news is when vallor, with his thing
> about kernels, builds 6.13 it won't blow up.

The word "pulled" in the URL is... unfortunate.

--
You're almost as happy as you think you are.

Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change
From: vallor
Newsgroups: comp.os.linux.advocacy
Date: Wed, 15 Jan 2025 14:05 UTC
References: 1 2
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: vallor@cultnix.org (vallor)
Newsgroups: comp.os.linux.advocacy
Subject: Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy
Microsoft code change
Date: 15 Jan 2025 14:05:45 GMT
Lines: 28
Message-ID: <luptlpFdacaU3@mid.individual.net>
References: <luofsuF6gdtU3@mid.individual.net> <vm8ca0$2ur3p$7@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net xZxcCdCPiom8jHZ6d+sr4A+MIMBzjsAIKtP+0Lftn/kV6jJjVH
Cancel-Lock: sha1:+tA61ESdqale5djhOmoKmitX55Y= sha256:HVBSDo1G2lQKtNTWyht4ses5e4KaaX8/VztONx9AMPg=
X-Face: +McU)#<-H?9lTb(Th!zR`EpVrp<0)1p5CmPu.kOscy8LRp_\u`:tW;dxPo./(fCl
CaKku`)]}.V/"6rISCIDP`
User-Agent: Pan/0.161 (Hmm2; c45f6052; Linux-6.12.9)
View all headers

On Wed, 15 Jan 2025 08:13:35 -0500, Chris Ahlstrom <OFeem1987@teleworm.us>
wrote in <vm8ca0$2ur3p$7@dont-email.me>:

> rbowman wrote this post while blinking in Morse code:
>
>> https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
>>
>> We're only here to help... The good news is when vallor, with his
>> thing about kernels, builds 6.13 it won't blow up.
>
> The word "pulled" in the URL is... unfortunate.

Indeed.

BTW, I looked at the lkml -- CONFIG_ARCH_HAS_EXECMEM_ROX no
longer autoselects for x86, but the code hasn't been removed (yet?).
So if you're feeling dangerous, you can turn it on.

I was running it yesterday...

_[/home/vallor/OS/linux-6.13-rc7]_(vallor@lm)🐧_
$ grep CONFIG_ARCH_HAS_EXECMEM_ROX .config
CONFIG_ARCH_HAS_EXECMEM_ROX=y

--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
OS: Linux 6.12.9 Release: Mint 21.3 Mem: 258G
"Have cursor, will curse."

1

rocksolid light 0.9.8
clearnet tor