Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #684015 > unrolled thread

Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change

Back to article view | Back to comp.os.linux.advocacy

Contents

  Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change rbowman <bowman@montana.com> - 2025-01-15 01:04 +0000
    Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change vallor <vallor@cultnix.org> - 2025-01-15 01:47 +0000
      Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change rbowman <bowman@montana.com> - 2025-01-15 06:13 +0000
    Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-15 08:13 -0500
      Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change vallor <vallor@cultnix.org> - 2025-01-15 14:05 +0000
    Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Farley Flud <fsquared@fsquared.linux> - 2025-01-16 13:27 +0000
      Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 11:29 -0600
        Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Farley Flud <fsquared@fsquared.linux> - 2025-01-16 17:52 +0000

#684015 — Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change

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.

[toc] | [next] | [standalone]

#684024

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."

[toc] | [prev] | [next] | [standalone]

#684043

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. 

[toc] | [prev] | [next] | [standalone]

#684064

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.

[toc] | [prev] | [next] | [standalone]

#684071

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."

[toc] | [prev] | [next] | [standalone]

#684126

On Wed, 15 Jan 2025 01:04:32 +0000, rbowman wrote:

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

This has got to be one the shittiest articles that I have ever read.

It has ZERO information.

After reading this I have no idea what the fuck is going on.

It concerns, I think, ROX or "read only executable pages" but how
or what effect they have is never explained.

The article is pure garbage.


-- 
Hail Linux!  Hail FOSS!  Hail Stallman!

[toc] | [prev] | [next] | [standalone]

#684138

On 1/16/25 7:27 AM, Farley Flud wrote:
> On Wed, 15 Jan 2025 01:04:32 +0000, rbowman wrote:
> 
>> https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
>>
> 
> This has got to be one the shittiest articles that I have ever read.
> 
> It has ZERO information.
> 
> After reading this I have no idea what the fuck is going on.
> 
> It concerns, I think, ROX or "read only executable pages" but how
> or what effect they have is never explained.
> 
> The article is pure garbage.
> 
> 



Last sentence:

    "Petkov will not be the only one wondering how the change made it in 
without a review by the Linux x86/x86_64 maintainers."


Moles among Linux developers, probably?

In Iran of Shah's time, when an armed anti-government political group 
formed (many of them sprang up in the last ten years of that regime), 
all SAVAK needed to do to destroy such groups was to create a similar 
one in its proximity.

Then, gradually, this bogus group after some harmless scores, made 
attempts to connect with the real one. After a few months or at most a 
year or two, some connections would get established. Then ideas of 
"joining forces to get stronger" would gradually get brought up until at 
last the two groups joined. Then the silent slaughter would take place.

This was also one of the Capone style methods in the 1920s to get rid of 
their competitors.

Mr. Windows, it seems, is practicing it too.

[toc] | [prev] | [next] | [standalone]

#684140

On Thu, 16 Jan 2025 11:29:35 -0600, Physfitfreak wrote:

> 
>     "Petkov will not be the only one wondering how the change made it in 
> without a review by the Linux x86/x86_64 maintainers."
> 
> 
> Moles among Linux developers, probably?
> 
> 
> This was also one of the Capone style methods in the 1920s to get rid of 
> their competitors.
> 
> Mr. Windows, it seems, is practicing it too.
>

It's an ancient practice.

Another example is if you meet an "underage" girl on the Internet it is
very likely a police officer. 




-- 
Hail Linux!  Hail FOSS!  Hail Stallman!

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.advocacy

csiph-web