linux-kernel - Re: [PATCH v7 0/6] cgroup, blkcg: prevent dirty inodes to pin dying memory cgroups

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]

Message-ID: <YLq3zb4saO9AMYCi@slm.duckdns.org>
Date:   Fri, 4 Jun 2021 19:31:25 -0400
From:   Tejun Heo <tj@...nel.org>
To:     Roman Gushchin <guro@...com>
Cc:     Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Dennis Zhou <dennis@...nel.org>,
        Dave Chinner <dchinner@...hat.com>, cgroups@...r.kernel.org
Subject: Re: [PATCH v7 0/6] cgroup, blkcg: prevent dirty inodes to pin dying
 memory cgroups

Hello,

On Fri, Jun 04, 2021 at 03:24:38PM -0700, Roman Gushchin wrote:
> I agree that switching to the nearest ancestor makes sense. If I remember
> correctly, I was doing this in v1 (or at least planned to do), but then
> switched to zeroing the pointer and then to bdi's wb.
>
> I fixed it in v8 and pushed it here: https://github.com/rgushchin/linux/tree/cgwb.8 .
> I'll wait a bit for Jan's and others feedback and will post v8 on Monday.
> Hopefully, it will be the final version.

Sounds great.

> Btw, how are such patches usually routed? Through Jens's tree?

I think the past writeback patches went through -mm.

Thanks.

-- 
tejun