linux-kernel - Re: [syzbot ci] Re: rust: zpool: add API for C and Rust

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: <3cbe68f0-c449-4634-b5a1-690b3eaf33ca@suse.cz>
Date: Fri, 26 Sep 2025 16:27:20 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Nhat Pham <nphamcs@...il.com>, Vitaly Wool <vitaly.wool@...sulko.se>
Cc: Johannes Weiner <hannes@...xchg.org>,
 syzbot ci <syzbot+cica6a1c285444b25f@...kaller.appspotmail.com>,
 a.hindborg@...nel.org, akpm@...ux-foundation.org, alex.gaynor@...il.com,
 aliceryhl@...gle.com, bjorn3_gh@...tonmail.com, boqun.feng@...il.com,
 chengming.zhou@...ux.dev, dakr@...nel.org, david@...hat.com,
 gary@...yguo.net, gregkh@...uxfoundation.org, liam.howlett@...cle.com,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org,
 lorenzo.stoakes@...cle.com, lossin@...nel.org, mhocko@...e.com,
 minchan@...nel.org, ojeda@...nel.org, rppt@...nel.org,
 rust-for-linux@...r.kernel.org, senozhatsky@...omium.org, surenb@...gle.com,
 tmgross@...ch.edu, yosry.ahmed@...ux.dev, syzbot@...ts.linux.dev,
 syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot ci] Re: rust: zpool: add API for C and Rust

On 9/24/25 19:38, Nhat Pham wrote:
> On Tue, Sep 23, 2025 at 10:46 PM Vitaly Wool <vitaly.wool@...sulko.se> wrote:
>>
>> LOL, no, forgot to run git commit --amend so came up with a wrong version.
>>
>> The Rust version is correct though.
>>
>> > This also still proposes an API with no in-kernel user.
>>
>> That's not correct, zsmalloc is the user.
> 
> A single user does not an API make.

IIRC what was suggested is to implement the zsmalloc API directly. What does
the extra inline function layer get us in case of a compile-time switch?

And do you need the Rust abstraction or just can make it part of the zblock
itself? You don't expect there to be more Rust-based backends than zblock, no?