linux-kernel - Re: [GIT pull] x86/urgent for 5.10-rc1

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] [day] [month] [year] [list]

Message-ID: <87sga23zj8.fsf@nanos.tec.linutronix.de>
Date:   Sun, 25 Oct 2020 19:56:27 +0100
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [GIT pull] x86/urgent for 5.10-rc1

On Sun, Oct 25 2020 at 11:34, Linus Torvalds wrote:
> On Sun, Oct 25, 2020 at 7:25 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>>
>> Restore the original #DE Oops message so tools which parse crash or dmesg
>> find what they expect.
>
> Hmm. I already got this one from Borislav as a different commit
> (5f1ec1fd3225: "x86/traps: Fix #DE Oops message regression"), so I'm

Hrm. Why didn't I notice?

> skipping this pull request as unnecessary.

Sure.

> I'm assuming nobody has based any work on top of it, and if they have,
> it's not the end of the world to get the duplicate commit, but it
> seems pointless to do a pull that ends up with no code changes at all
> for me.

Fair enough.