linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huang Jianan <huangjianan@oppo.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Chengguang Xu <cgxu519@mykernel.net>,
	Miklos Szeredi <mszeredi@redhat.com>,
	overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH] ovl: set overlayfs inode's a_ops->direct_IO properly
Date: Thu, 30 Sep 2021 16:11:02 +0800	[thread overview]
Message-ID: <39bf616b-d962-4295-f7a4-e120ad569d7d@oppo.com> (raw)
In-Reply-To: <CAJfpegsJuprveXYHCz7wu11nZU2ZG+pOQ6Jy--PSO6Km1VnTng@mail.gmail.com>

在 2021/9/30 16:02, Miklos Szeredi 写道:
> On Thu, 30 Sept 2021 at 08:52, Huang Jianan <huangjianan@oppo.com> wrote:
>> This patch can ensure that loop devices based on erofs and overlayfs
>> can't set dio through __loop_update_dio.
> So does this mean that you tested the "loop on overlayfs on erofs"
> setup and it works?
Yes, I think this has always been able to work normally. But recently we
found  that the direct_IO flag will be set incorrectly in the Android apex
scenario, which leads to oops.

With this patch, Android apex can work normally through loop on overlayfs
on erofs using bufferd IO.

Thanks,
Jianan
> Thanks,
> Miklos


  reply	other threads:[~2021-09-30  8:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 12:47 [PATCH] ovl: set overlayfs inode's a_ops->direct_IO properly Chengguang Xu
2021-09-30  6:52 ` Huang Jianan
2021-09-30  6:54   ` Chengguang Xu
2021-09-30  8:02   ` Miklos Szeredi
2021-09-30  8:11     ` Huang Jianan [this message]
2021-09-30 12:55 ` Miklos Szeredi
2021-10-03 14:41   ` Chengguang Xu
2021-10-07 12:09     ` Miklos Szeredi
2021-10-12  7:41       ` Chengguang Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39bf616b-d962-4295-f7a4-e120ad569d7d@oppo.com \
    --to=huangjianan@oppo.com \
    --cc=cgxu519@mykernel.net \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).