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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 5 Jun 2020 14:20:35 -0700
From:   Brendan Higgins <>
To:     Shuah Khan <>,
        Alan Maguire <>
Cc:     David Gow <>,
        Patricia Alfonso <>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        KUnit Development <>,
        Linux Kernel Mailing List <>
Subject: Re: [PATCH v4 kunit-next 0/2] kunit: extend kunit resources API

On Fri, May 29, 2020 at 2:46 PM Alan Maguire <> wrote:
> A recent RFC patch set [1] suggests some additional functionality
> may be needed around kunit resources.  It seems to require
> 1. support for resources without allocation
> 2. support for lookup of such resources
> 3. support for access to resources across multiple kernel threads
> The proposed changes here are designed to address these needs.
> The idea is we first generalize the API to support adding
> resources with static data; then from there we support named
> resources.  The latter support is needed because if we are
> in a different thread context and only have the "struct kunit *"
> to work with, we need a way to identify a resource in lookup.
> [1]
> Changes since v3:
> - removed unused "init" field from "struct kunit_resources" (Brendan)

Shuah, it looks like you haven't sent a PR to Linus yet. Would you
mind picking this up for 5.8?

Powered by blists - more mailing lists