linux-kernel - Re: [PATCH] kernfs: support kernfs notify in memory recliam context

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 16 Nov 2023 09:04:34 -0800
From:   junxiao.bi@...cle.com
To:     Mariusz Tkaczyk <mariusz.tkaczyk@...ux.intel.com>,
        Song Liu <song@...nel.org>
Cc:     Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org,
        linux-raid@...r.kernel.org, gregkh@...uxfoundation.org
Subject: Re: [PATCH] kernfs: support kernfs notify in memory recliam context

On 11/15/23 7:30 AM, Mariusz Tkaczyk wrote:

> On Tue, 14 Nov 2023 15:53:47 -0800
> junxiao.bi@...cle.com wrote:
>
>> Understood, thanks. Sound like depending on Userspace on memory reclaim
>> path is really bad idea and the only option for fixing it is to remove
>> that dependency, but i am not sure that is possible without breaking the
>> consistency of metadata.
>>
>> Thanks,
>>
>> Junxiao.
> Indeed the project of external metadata management if fragile. You cares about
> IMSM here (same as me) so ideally we should implement metadata management in
> kernel- I think that IMSM deserved that after 10 years on the market. There is
> no better option, other options are just "workarounds" for the lack of metadata
> management in kernel.
Agree, sound like that's the way to proceed.
>
> Song, any comments here?
>
>  From the second hand, there is native raid which should just work, so maybe you
> can switch to the native raid?

Unfortunately that's is not possible, it's a production setup to use 
imsm raid.

Thanks,

Junxiao.

>
> Thanks,
> Mariusz