linux-kernel - Re: [syzbot ci] Re: mm/vmalloc: clarify why vmap_range

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: <DETCJPVHXE8O.2A2XQ73M2QOGK@google.com>
Date: Tue, 09 Dec 2025 02:56:45 +0000
From: Brendan Jackman <jackmanb@...gle.com>
To: syzbot ci <syzbot+cie262549d3c7e101a@...kaller.appspotmail.com>, 
	<akpm@...ux-foundation.org>, <jackmanb@...gle.com>, 
	<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>, <urezki@...il.com>
Cc: <syzbot@...ts.linux.dev>, <syzkaller-bugs@...glegroups.com>
Subject: Re: [syzbot ci] Re: mm/vmalloc: clarify why vmap_range_noflush()
 might sleep

On Mon Dec 8, 2025 at 8:51 AM UTC, syzbot ci wrote:
> kernel build error
>
> tree:      mm-new
> URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base:      3f43be96f919cc611dcb2a4e38dd464831f4513e
> arch:      amd64

Um, so apparently I didn't even compile this code for x86? Sorry about
this.

FWIW, I do test my patches [0]! Apparently in this case I just decided
to post it without actually checking the results.

[0] https://github.com/bjackman/limmat-kernel-nix