Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sun, 8 Apr 2018 12:55:34 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Al Viro <viro@ZenIV.linux.org.uk>
Cc:     Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Mateusz Guzik <mguzik@redhat.com>
Subject: Re: linux-next: build failure after merge of the vfs tree
Message-ID: <20180408125534.7c448b0e@canb.auug.org.au>
In-Reply-To: <20180408021945.GF30522@ZenIV.linux.org.uk>
References: <20180319170627.04eae43b@canb.auug.org.au>
        <20180403122629.688f2cab@canb.auug.org.au>
        <20180408021945.GF30522@ZenIV.linux.org.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 boundary="Sig_/.5RYdJnxbrVO40Ee=K0D7h_"; protocol="application/pgp-signature"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--Sig_/.5RYdJnxbrVO40Ee=K0D7h_
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Al,

On Sun, 8 Apr 2018 03:19:56 +0100 Al Viro <viro@ZenIV.linux.org.uk> wrote:
>
> > > Caused by commit
> > >=20
> > >   92afc556e622 ("buffer.c: call thaw_super during emergency thaw")
> > >=20
> > > I have reverted that commit for today. =20
> >=20
> > I am still doing that revert ... =20
>=20
> That's interesting, seeing that this commit is *not* in #for-next and
> 08fdc8a0138a should not have that problem...

I do the revert by applying a reverse patch (initially generated by a
"git revert").  That reverse patch still applies cleanly, so I have no
easy way to tell that this problem has been fixed (except by trying
without the reverse patch each day - which would add a significant cost
to my work as that patch touches linux/fs.h).

Anyway, thanks for letting me know, I will remove the reverse patch
from tomorrow.
--=20
Cheers,
Stephen Rothwell

--Sig_/.5RYdJnxbrVO40Ee=K0D7h_
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAlrJhKYACgkQAVBC80lX
0GyUmQf8C7CmgwHe+kTiEbFeaAbFoY/77ZSY56+VLQJ+df7PZa6HzfrAiG7FpJLG
LEiczUtxpnaVp2jekc+ZNcXFds2lyC/WGnINRCaPuLFctk3s0WM0PnAWcvDDMxgS
oFwpO14fQTpBsp/Yz5iLR68a2HteicJD7rjuG9gkHCLk3hvHGIZj+g5iTk8Tjb/n
rpAz27WzBD9NOYLnQt6WS0dTcDf++z4UPUolzb6GD75mVYYFMlLHjEEKMajxnzOa
Sxtz5nrofL4Lsy+DqYUE7Xatmac2///1/NxnXkJJXxpe1AcyLRtr6Wl6MkG24mTp
D4qbyCaFYIr0EygMZ/Zt90cO3H0Bwg==
=RFRw
-----END PGP SIGNATURE-----

--Sig_/.5RYdJnxbrVO40Ee=K0D7h_--