Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 9 May 2023 02:25:59 +0200
From:   Jan Kara <jack@suse.cz>
To:     youling257 <youling257@gmail.com>
Cc:     jack@suse.cz, hch@infradead.org, hch@lst.de,
        linux-ext4@vger.kernel.org, ritesh.list@gmail.com, tytso@mit.edu
Subject: Re: [PATCH v4 12/13] ext4: Stop providing .writepage hook
Message-ID: <20230509002559.tudxwmu2xn3valw3@quack3>
References: <20221207112722.22220-12-jack@suse.cz>
 <20230508175108.6986-1-youling257@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230508175108.6986-1-youling257@gmail.com>
Precedence: bulk

Hello,

On Tue 09-05-23 01:51:08, youling257 wrote:
> I using linux mainline kernel on android.
> https://github.com/youling257/android-mainline/commits/6.4
> https://github.com/youling257/android-mainline/commits/6.3 "ext4: Stop
> providing .writepage hook" cause some android app unable to read
> storage/emulated/0 files, i need to say android esdfs file system
> storage/emulated is ext4 data/media bind mount.  I want to ask, why
> android storage/emulated need .writepage hook?

Honestly, I don't know. I guess you need to look into implementation of
esdfs in the Android kernel and why it needs filesystem's .writepage
hook...

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR