linux-kernel - Re: [GIT PULL] dma-mapping fix for Linux 6.19

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: <CAHk-=wgpWEoW1VKZv-7YC_oftbqWXh3xERYBsjfv5dc-MO-Lmg@mail.gmail.com>
Date: Mon, 22 Dec 2025 10:03:42 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Marek Szyprowski <m.szyprowski@...sung.com>, 
	Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, iommu@...ts.linux.dev, 
	Christoph Hellwig <hch@....de>, Robin Murphy <robin.murphy@....com>, Leon Romanovsky <leon@...nel.org>
Subject: Re: [GIT PULL] dma-mapping fix for Linux 6.19

On Mon, 22 Dec 2025 at 08:03, Marek Szyprowski <m.szyprowski@...sung.com> wrote:
>
> Leon Romanovsky (1):
>       parisc: Set valid bit in high byte of 64‑bit physical address

Heh. Pulled and pushed out, but in the process it triggered a
mis-feature in the kernel.org hooks.

That commit message uses the UTF8 character U+2011 for 'Non-Breaking
Hyphen' in that "64‑bit" thing (and then the same character is also in
the commit message when it talks about 32‑bit systems).

Which is all good and correct, and I'm not complaining about your pull
request. A NB hyphen is certainly not incorrect here.

But it's apparently unusual enough that some of our infrastructure for
the activity feed on kernel.org goes all wonky, and that scripting
then complains about

   remote: UnicodeEncodeError: 'ascii' codec can't encode character
'\u2011' in position 90: ordinal not in range(128)

and I wonder if that's why I also haven't seen a pr-tracker-bot reply
to your email yet (but it might also be that I'm just too quick to
blame things, and it's just delayed a bit).

Konstantin - I think it's only the subject line that matters here,
because if it reacted to non-ASCII characters in commit messages, I'd
have seen this issue many times before. I'll send you the whole
traceback separately, although I suspect you can easily just re-create
this issue locally.

                 Linus