Date:   Tue, 16 Nov 2021 09:17:02 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Steve French <smfrench@gmail.com>,
        CIFS <linux-cifs@vger.kernel.org>
Cc:     chiminghao <chi.minghao@zte.com.cn>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the cifs tree
Message-ID: <20211116091702.3e2c4550@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/8OU1EBP8FYM4_smUQbePUaG";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/8OU1EBP8FYM4_smUQbePUaG
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

After merging the cifs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

In file included from fs/cifs/dns_resolve.c:18:
fs/cifs/cifsglob.h: In function 'cifs_get_tlink':
fs/cifs/cifsglob.h:1169:14: error: passing argument 1 of 'atomic_inc' from =
incompatible pointer type [-Werror=3Dincompatible-pointer-types]
 1169 |   atomic_inc(&tlink->tl_count);
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              refcount_t * {aka struct refcount_struct *}
In file included from include/linux/atomic.h:82,
                 from include/linux/cpumask.h:13,
                 from include/linux/smp.h:13,
                 from include/linux/lockdep.h:14,
                 from include/linux/spinlock.h:62,
                 from include/linux/mmzone.h:8,
                 from include/linux/gfp.h:6,
                 from include/linux/slab.h:15,
                 from fs/cifs/dns_resolve.c:15:
include/linux/atomic/atomic-instrumented.h:179:22: note: expected 'atomic_t=
 *' but argument is of type 'refcount_t *' {aka 'struct refcount_struct *'}
  179 | atomic_inc(atomic_t *v)
      |            ~~~~~~~~~~^

and lots more similar ...

Caused by commit

  ef242296e441 ("fs:cifs: convert from atomic_t to refcount_t on tlink->tl_=
count")

Please write, review, test (repeat) and, only then, publish. :-(

I have used the cifs tree from next-20211115 for today.

--=20
Cheers,
Stephen Rothwell

--Sig_/8OU1EBP8FYM4_smUQbePUaG
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmGS3F4ACgkQAVBC80lX
0Gwl7wf/fkkYyUfQl2BCCbBUhVHjlIigMz/u91Z+nugFkijukO6d00ef5TcemlM+
HwTZWmsakV0AdtwBa3tIGY+4NFy1xpSMsGoBjhbcS9pQAXnkVzxa1OTtync2nGUZ
8M5z4LrKd+FmVZYqA3w3ekvDCQBZkbchrwBVEU+hurl8XUVrOFrFo7eO7KfFR74s
kGzIRVf/wrKD4RI0f0pDTyEjUKWyxX4O6YKDhPDHzPBQVs2VWaUSYuDOyAmlfmOZ
pIA5EcPW1C56c7ntFPvw+U9tP6jsKpzP3ajVmal9UcVk0+LAezAK74llJlSDHd9F
Wla1vfjpLmqsTnwqPHlsQw4IJsjp+g==
=xtMQ
-----END PGP SIGNATURE-----

--Sig_/8OU1EBP8FYM4_smUQbePUaG--