linux-kernel - Re: linux-next: build failure after merge of the block tree

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: <493fac19-4299-4d8c-823b-12eaa79ce010@kernel.dk>
Date: Mon, 19 Jan 2026 13:31:46 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Mark Brown <broonie@...nel.org>
Cc: Tamir Duberstein <tamird@...il.com>, Miguel Ojeda <ojeda@...nel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>,
 Andreas Hindborg <a.hindborg@...nel.org>
Subject: Re: linux-next: build failure after merge of the block tree

On 1/19/26 11:20 AM, Mark Brown wrote:
> On Mon, Jan 19, 2026 at 11:05:17AM -0700, Jens Axboe wrote:
>> On 1/19/26 11:02 AM, Mark Brown wrote:
> 
>>> Caused by commit
> 
>>>   4cef2fcda3ada (rnull: replace `kernel::c_str!` with C-Strings)
> 
>>> I have used the version from 20260116 instead.
> 
>> Adding Andreas too. This is a bit annoying as other stuff in the
>> block/io_uring tree would be nice to get exposed...
> 
> Like I said in the other mail it turns out this has been there for a
> while (something has triggered the rust build I think, I *thought* I'd
> had the toolchain on the build machine already but ICBW and might've put
> it on after the release on Friday) so I'm going to do a revert instead
> and everything else will get picked up.

Perfect, thanks!

-- 
Jens Axboe