linux-kernel - Re: [GIT PULL] HID for 6.11

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: <20240722-marvellous-talented-magpie-ef4ca9@lemur>
Date: Mon, 22 Jul 2024 09:58:18 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Konrad Dybcio <konrad.dybcio@...aro.org>, 
	Benjamin Tissoires <bentiss@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, 
	Jiri Kosina <jikos@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] HID for 6.11

On Mon, Jul 22, 2024 at 03:32:48PM GMT, Krzysztof Kozlowski wrote:
> > this commit broke b4 for everyone starting next-20240719, as it's
> > an empty cover letter with b4 tracking information
> 
> Konrad gave me idea which could at least protect final tree from such
> mistakes - commit hook for merges, something like:
> 
> https://github.com/krzk/tools/blob/master/linux/verify_b4.sh
> https://github.com/krzk/tools/blob/master/linux/git-hooks-post-merge

I'll include something like this into the contrib section.

Unfortunately, I'm not sure we can ever completely avoid this, but perhaps
linux-next can add a check to see if any of the commits in a merge contain
"--b4-submit-tracking--" and then refuse to consider it?

-K