linux-kernel - Re: [GIT PULL] EFI urgent fixes

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]

Date:	Mon, 2 Mar 2015 13:35:14 +0000
From:	Matt Fleming <matt@...eblueprint.co.uk>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>,
	Yinghai Lu <yinghai@...nel.org>, linux-efi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] EFI urgent fixes

On Mon, 02 Mar, at 02:24:10PM, Ingo Molnar wrote:
> 
> Pulled, thanks Matt!
> 
> For future reference, plase leave out unreadable commit messages like 
> this:
> 
>   While adding support loading kernel and initrd above 4G to grub2 in 
>   legacy mode, I was referring to efi_high_alloc(). That will allocate 
>   buffer for kernel and then initrd, and initrd will use kernel buffer 
>   start as limit.
> 
>   During testing found two buffers will be overlapped when initrd size 
>   is very big like 400M.
> 
> I pulled it, because you do explain the commit in the second half of 
> the changelog, in parentheses - but instead of forcing readers through 
> the crappy part, please just drop the crappy explanation and fix it 
> up, or require your contributors to submit proper changelogs. (Yinghai 
> Lu is a repeat offender in that area.)

Noted, I'll be sure to do this in the future. Thanks Ingo!

-- 
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/