linux-kernel - Re: [GIT pull] x86/urgent for v6.11-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wjw=FsFkF9EhF1ZzM9QUG0Az1_hk++9GU3ZffwafDLNgg@mail.gmail.com>
Date: Sun, 11 Aug 2024 10:30:52 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [GIT pull] x86/urgent for v6.11-rc3

On Sun, 11 Aug 2024 at 06:58, Thomas Gleixner <tglx@...utronix.de> wrote:
>
>   - Don't make acpi_mp_wake_mailbox not read only after init [..]

I assume there's one negation too many there, and it should just be
"Don't make acpi_mp_wake_mailbox read-only".

Also, while parsing the merge message and looking at the patch to make
sure I got it right, it struck me that it would have been really nice
to have found this "non-init function writes to __ro_after_init
variable" automatically.

Sadly, our section analysis is purely based on "this section has a
reference to that other section", and thus cannot see what kind of
access it is. And I'm not seeing how to try to figure that kind of
thing out without lots of work (ie objtool kind of stuff), so I guess
we're stuck with figuring these things out manually.

Oh well.

            Linus