From: Miklos Szeredi <miklos@szeredi.hu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH 5/7] ovl: avoid possible inode number collisions with xino=on
Date: Wed, 19 Feb 2020 20:45:39 +0100 [thread overview]
Message-ID: <CAJfpegs=YniZqHLXUkD8zjz5ssjgQvAZE08RzQVw-JwYRVv_mA@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxieagY4hW9jHsHpPVsiRFo3CAThdc6=CcmPR-aOPtnjDQ@mail.gmail.com>
On Wed, Feb 19, 2020 at 4:59 PM Amir Goldstein <amir73il@gmail.com> wrote:
>
> > > Yeh, it's mostly the same. Branch ovl-ino is already rebased.
> > > If you have no other comments, I'll prepare v2 and test it with 5.6-rc2.
> >
> > Thanks. I've already applied the patches leading up to this and just
> > pushed to #overlayfs-next.
> >
>
> OK, I'll rebase the rest on top of that.
> While you are here, what do you think about:
> ovl: enable xino automatically in more cases
>
> Do you agree with that minor change of behavior?
I haven't thought about that yet.
>
> BTW, I see that overlayfs-next allows all remote fs as upper,
> without extra restrictions.
> I guess you are not too worried about implications?
> Or intend to fix that up before the merge window?
No, I'm not too worried, but if you send a patch, I'm not against
restricting it either.
Thanks,
Miklos
next prev parent reply other threads:[~2020-02-19 19:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 17:58 [PATCH 0/7] Sort out overlay ino numbers Amir Goldstein
2020-01-01 17:58 ` [PATCH 1/7] ovl: fix value of i_ino for lower hardlink corner case Amir Goldstein
2020-01-01 17:58 ` [PATCH 2/7] ovl: fix out of date comment and unreachable code Amir Goldstein
2020-01-01 17:58 ` [PATCH 3/7] ovl: factor out helper ovl_get_root() Amir Goldstein
2020-01-01 17:58 ` [PATCH 4/7] ovl: simplify i_ino initialization Amir Goldstein
2020-01-01 17:58 ` [PATCH 5/7] ovl: avoid possible inode number collisions with xino=on Amir Goldstein
2020-02-19 14:25 ` Miklos Szeredi
2020-02-19 15:28 ` Amir Goldstein
2020-02-19 15:36 ` Miklos Szeredi
2020-02-19 15:59 ` Amir Goldstein
2020-02-19 19:45 ` Miklos Szeredi [this message]
2020-02-21 1:10 ` Amir Goldstein
2020-01-01 17:58 ` [PATCH 6/7] ovl: enable xino automatically in more cases Amir Goldstein
2020-01-01 17:58 ` [PATCH 7/7] ovl: document xino expected behavior Amir Goldstein
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='CAJfpegs=YniZqHLXUkD8zjz5ssjgQvAZE08RzQVw-JwYRVv_mA@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
/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).