linux-kernel - Re: [PATCH] kthread: Export kthread

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: <11243edc-22b2-6d07-c2b7-b83a6dd09308@redhat.com>
Date:   Tue, 13 Feb 2018 16:42:00 -0500
From:   Waiman Long <longman@...hat.com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Tejun Heo <tj@...nel.org>, Ingo Molnar <mingo@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kthread: Export kthread_data()

On 02/13/2018 04:40 PM, Waiman Long wrote:
> On 02/13/2018 10:50 AM, Christoph Hellwig wrote:
>> On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote:
>>> When multiple kernel threads are created to cooperatively work on
>>> a common task, we may need a convenient way to access data that are
>>> specific to each kthread.
>>>
>>> The kthread_data() function fits this need.  However, it was not
>>> visible to kthreads started in a kernel module. To solve this problem,
>>> the kthread_data() function is now exported allowing kthreads from
>>> kernel modules to use it.
>> Please send this along wit hthe actual user of it.
> It is the developers of the dm-vdo/kvdo modules that would like to use
> the kthread_data() function. See
>
> https://github.com/dm-vdo/kvdo
>
> Those modules have a bunch of kernel threads working on block storage
> deduplication/compression.
>
> -Longman
>
BTW, I am fine with not exporting the function. They just have to find
an alternative way of doing it.

-Longman