linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the vhost tree
Date: Mon, 16 Dec 2019 14:49:40 +1100	[thread overview]
Message-ID: <20191216144940.014b2aa7@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

Hi all,

After merging the vhost tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:

In file included from include/linux/list.h:9,
                 from include/linux/preempt.h:11,
                 from include/linux/spinlock.h:51,
                 from include/linux/seqlock.h:36,
                 from include/linux/time.h:6,
                 from include/linux/stat.h:19,
                 from include/linux/fcntl.h:5,
                 from include/linux/eventfd.h:12,
                 from drivers/vhost/vhost.c:13:
drivers/vhost/vhost.c: In function 'vhost_log_write':
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types lacks a cast
  844 |   (!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
      |                             ^~
include/linux/kernel.h:858:4: note: in expansion of macro '__typecheck'
  858 |   (__typecheck(x, y) && __no_side_effects(x, y))
      |    ^~~~~~~~~~~
include/linux/kernel.h:868:24: note: in expansion of macro '__safe_cmp'
  868 |  __builtin_choose_expr(__safe_cmp(x, y), \
      |                        ^~~~~~~~~~
include/linux/kernel.h:877:19: note: in expansion of macro '__careful_cmp'
  877 | #define min(x, y) __careful_cmp(x, y, <)
      |                   ^~~~~~~~~~~~~
drivers/vhost/vhost.c:1968:11: note: in expansion of macro 'min'
 1968 |   u64 l = min(log[i].len, len);
      |           ^~~

Introduced by commit

  b072ae74df17 ("vhost: use vhost_desc instead of vhost_log")

vhost_log::len was u64 and vhost_desc::len is u32 and len is u64.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-12-16  3:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  3:49 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23  4:10 linux-next: build warning after merge of the vhost tree Stephen Rothwell
2023-03-22  1:32 Stephen Rothwell
2023-03-22  2:24 ` Michael S. Tsirkin
2022-12-19 23:59 Stephen Rothwell
2022-12-20  6:01 ` Michael S. Tsirkin
2022-12-20  7:04   ` Ricardo Cañuelo
2022-08-11  1:59 Stephen Rothwell
2022-08-11  6:45 ` Ricardo Cañuelo
2022-03-07  4:40 Stephen Rothwell
2022-03-07  6:46 ` Xuan Zhuo
2022-03-07  9:17   ` Michael S. Tsirkin
2022-03-07  9:41     ` Xuan Zhuo
2022-03-07 10:12   ` Stephen Rothwell
2022-03-07 11:00     ` Michael S. Tsirkin
2022-03-09  6:13       ` Stephen Rothwell
2022-03-09  6:15         ` Xuan Zhuo
2022-03-09  6:30           ` Xuan Zhuo
2021-07-06  2:37 Stephen Rothwell
2020-06-09  3:25 Stephen Rothwell
2019-11-15  4:36 Stephen Rothwell

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=20191216144940.014b2aa7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mst@redhat.com \
    /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).