linux-kernel - Re: [PATCH] checkpatch: Add support for long UTF-8 name

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: <20260105141606.688aa8f7@kmaincent-XPS-13-7390>
Date: Mon, 5 Jan 2026 14:16:06 +0100
From: Kory Maincent <kory.maincent@...tlin.com>
To: linux-kernel@...r.kernel.org
Cc: Jérémie Dautheribes <jeremie.dautheribes@...tlin.com>,
 Louis Chauvet <louis.chauvet@...tlin.com>, thomas.petazzoni@...tlin.com,
 Andy Whitcroft <apw@...onical.com>, Joe Perches <joe@...ches.com>,
 Dwaipayan Ray <dwaipayanray1@...il.com>, Lukas Bulwahn
 <lukas.bulwahn@...il.com>
Subject: Re: [PATCH] checkpatch: Add support for long UTF-8 name

On Fri, 28 Nov 2025 11:26:22 +0100
Kory Maincent <kory.maincent@...tlin.com> wrote:

> In case we have a long utf-8 name the second line will contain UTF-8
> code.
> 
> Here is an example:
>   From: =?UTF-8?q?K=C3=B6ry=20Maincent=20=28bla=20blou=20prout=20test=20?=
>    =?UTF-8?q?=29?= <kory.maincent@...tlin.com>
>   Date: Fri, 28 Nov 2025 10:57:00 +0100
>   Subject: [PATCH] checkpatch: Add support for long UTF-8 name
> 
> On this rare case checkpatch is returning an error due to UTF-8 code in
> the name as it only decodes the From once the line is fully concatenated.
>   WARNING: From:/Signed-off-by: email name mismatch: 'From: "Köry Maincent
>   (bla blou prout test test=?UTF-8?q?=29?=" <kory.maincent@...tlin.com>'
>   != 'Signed-off-by: Köry Maincent (bla blou prout test test)
>   <kory.maincent@...tlin.com>'
> 
> Decode each line instead to be sure we don't have UTF-8 code in the
> email name check.

Hello,

Any news on this? I know it fixes a rare case but still, the issue is present.

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com