From: CAI Qian <caiqian@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Miklos Szeredi <mszeredi@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [bisected] Re: docker overlay support broken post v4.8
Date: Thu, 13 Oct 2016 16:46:50 -0400 (EDT) [thread overview]
Message-ID: <1846057861.808141.1476391610699.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161013204058.GT19539@ZenIV.linux.org.uk>
----- Original Message -----
> From: "Al Viro" <viro@ZenIV.linux.org.uk>
> Sent: Thursday, October 13, 2016 4:40:58 PM
> Subject: Re: [bisected] Re: docker overlay support broken post v4.8
>
> > Reverted the patchset of "Xattr inode operation removal" against the latest
> > mainline
> > fixed the problem, i.e., commits below in order.
> >
> > fd50ecaddf8372a1d96e0daeaac0f93cf04e4d42
> > 6c6ef9f26e598fb977f60935e109cd5b266c941a
> > bf3ee71363c0b44acb62f375aea470262ac4210a
> > 5d6c31910bc0713e37628dc0ce677dcb13c8ccf4
> > f5c244383725a6de06bc62fa7c54c0ea0d942eec
> > 5f6e59ae8277cef221fdbf9b12f0c4f80db59944
> > d0a5b995a308347fdb1bb0412df32acd0312523b
>
> Where in that branch has that started? Or is it interaction upon merge
> between two branches, each working on its own?
>
Everything is tested on the mainline's master branch. I just use 'git show'
the above commits and then 'patch -Np1 -R' to revert them.
CAI Qian
next prev parent reply other threads:[~2016-10-13 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1844859631.492693.1476279971647.JavaMail.zimbra@redhat.com>
2016-10-12 13:54 ` docker overlay support broken post v4.8 CAI Qian
2016-10-13 20:38 ` [bisected] " CAI Qian
2016-10-13 20:40 ` Al Viro
2016-10-13 20:46 ` CAI Qian [this message]
2016-10-13 21:16 ` Vivek Goyal
2016-10-13 21:39 ` Vivek Goyal
2016-10-13 21:48 ` Vivek Goyal
2016-10-14 1:08 ` Andreas Grünbacher
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=1846057861.808141.1476391610699.JavaMail.zimbra@redhat.com \
--to=caiqian@redhat.com \
--cc=agruenba@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=vgoyal@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/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).