linux-kernel - Re: [patch] x86/crash: fix crash_setup_memmap

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 16 Apr 2021 17:13:26 +0200
From:   Mike Galbraith <efault@....de>
To:     Borislav Petkov <bp@...en8.de>
Cc:     LKML <linux-kernel@...r.kernel.org>, DaveYoung <dyoung@...hat.com>,
        Baoquan He <bhe@...hat.com>, kexec@...ts.infradead.org,
        x86@...nel.org, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch] x86/crash: fix crash_setup_memmap_entries()
 out-of-bounds access

On Fri, 2021-04-16 at 16:44 +0200, Borislav Petkov wrote:
> On Fri, Apr 16, 2021 at 03:16:07PM +0200, Mike Galbraith wrote:
> > On Fri, 2021-04-16 at 14:16 +0200, Borislav Petkov wrote:
> > >
> > > Please be more verbose and structure your commit message like this:
> >
> > Hrmph, I thought it was too verbose for dinky one-liner if anything.
>
> Please look at how other commit messages in tip have free text - not
> only tools output.
>
> Also, this looks like a fix for some previous commit. Please dig out
> which commit introduced the issue and put its commit ID in a Fixes: tag
> above your S-o-B.
>
> If you don't have time or desire to do that, you can say so and I'll do
> it myself when I get a chance.

Ok, bin it for the nonce.

	-Mike