From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
linux-unionfs@vger.kernel.org,
Alexander Larsson <alexl@redhat.com>,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] ovl: require xwhiteout feature flag on layer roots
Date: Fri, 19 Jan 2024 14:19:38 +0200 [thread overview]
Message-ID: <CAOQ4uxhVwnhOLxbfAjeGkwXA2iOz=-BXZNKUtY29UN_zTDtfCg@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegteroc6yJAmjh=MaqZOO9Q7ZJfg5BgMJFN3wdHGZK6gGw@mail.gmail.com>
On Fri, Jan 19, 2024 at 1:20 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Fri, 19 Jan 2024 at 12:08, Amir Goldstein <amir73il@gmail.com> wrote:
>
> > > @@ -577,6 +580,8 @@ static int ovl_dir_read_impure(const struct path *path, struct list_head *list,
> > > INIT_LIST_HEAD(list);
> > > *root = RB_ROOT;
> > > ovl_path_upper(path->dentry, &realpath);
> > > + if (ovl_path_check_xwhiteouts_xattr(ofs, &ofs->layers[0], &realpath))
> > > + rdd.in_xwhiteouts_dir = true;
> >
> > Not needed since we do not support xwhiteouts on upper.
>
> Right.
>
> > > @@ -1079,6 +1090,8 @@ static int ovl_get_layers(struct super_block *sb, struct ovl_fs *ofs,
> > > l->name = NULL;
> > > ofs->numlayer++;
> > > ofs->fs[fsid].is_lower = true;
> > > +
> > > +
> >
> > extra spaces.
>
> Sorry, missing self review...
>
> > Do you want me to fix/test and send this to Linus?
>
> Yes please, if it's not a problem four you.
>
ok. queued.
Thanks,
Amir.
next prev parent reply other threads:[~2024-01-19 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:14 [PATCH v2] ovl: require xwhiteout feature flag on layer roots Miklos Szeredi
2024-01-19 11:08 ` Amir Goldstein
2024-01-19 11:20 ` Miklos Szeredi
2024-01-19 12:19 ` Amir Goldstein [this message]
2024-01-19 12:29 ` Alexander Larsson
2024-01-19 14:12 ` Amir Goldstein
2024-01-19 16:35 ` Alexander Larsson
2024-01-19 19:06 ` Amir Goldstein
2024-01-19 20:29 ` Miklos Szeredi
2024-01-20 10:32 ` Amir Goldstein
2024-01-22 10:01 ` Alexander Larsson
2024-01-22 8:38 ` Amir Goldstein
2024-01-22 10:44 ` Alexander Larsson
2024-01-22 11:30 ` 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='CAOQ4uxhVwnhOLxbfAjeGkwXA2iOz=-BXZNKUtY29UN_zTDtfCg@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=alexl@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=stable@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).