Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: Is it time to remove reiserfs?
To:     Matthew Wilcox <willy@infradead.org>, linux-kernel@vger.kernel.org,
        linux-fsdevel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
        Jan Kara <jack@suse.cz>
References: <YhIwUEpymVzmytdp@casper.infradead.org>
From:   Edward Shishkin <edward.shishkin@gmail.com>
Message-ID: <fbc744c9-e22f-138c-2da3-f76c3edfcc3d@gmail.com>
Date:   Mon, 21 Feb 2022 00:21:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <YhIwUEpymVzmytdp@casper.infradead.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 02/20/2022 01:13 PM, Matthew Wilcox wrote:
> Keeping reiserfs in the tree has certain costs.  For example, I would
> very much like to remove the 'flags' argument to ->write_begin.  We have
> the infrastructure in place to handle AOP_FLAG_NOFS differently, but
> AOP_FLAG_CONT_EXPAND is still around, used only by reiserfs.


Please, consider the patch (next email in the thread) which drops that
flag from reiserfs.

Thanks,
Edward.