netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	kbuild test robot <fengguang.wu@intel.com>,
	kvm@vger.kernel.org, netdev@vger.kernel.org,
	Liang Li <liang.z.li@intel.com>,
	virtualization@lists.linux-foundation.org,
	Wei Wang <wei.w.wang@intel.com>,
	kbuild-all@01.org, alexei.starovoitov@gmail.com
Subject: Re: [kbuild-all] [vhost:vhost 19/20] Warning: arch/x86/tools/test_get_len found difference at <pm_restore_gfp_mask>:ffffffff811aa5f0
Date: Thu, 8 Feb 2018 08:37:33 +0800	[thread overview]
Message-ID: <20180208003733.GA25579@intel.com> (raw)
In-Reply-To: <0e84111e-84bd-f31a-49c7-45bc7079aabf@iogearbox.net>

On Thu, Feb 08, 2018 at 01:25:39AM +0100, Daniel Borkmann wrote:
> On 02/08/2018 01:20 AM, Philip Li wrote:
> > On Thu, Feb 08, 2018 at 02:09:41AM +0200, Michael S. Tsirkin wrote:
> >> On Wed, Feb 07, 2018 at 03:02:57PM +0800, kbuild test robot wrote:
> >>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost
> >>> head:   96bcd04462b99e2c80e09f6537770a0ca6b288d0
> >>> commit: cc1d1dc07885803981520a5303ef5b130f2ca2e8 [19/20] mm: support reporting free page blocks
> >>> config: x86_64-rhel
> >>> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> >>> reproduce:
> >>>         git checkout cc1d1dc07885803981520a5303ef5b130f2ca2e8
> >>>         # save the attached .config to linux build tree
> >>>         make ARCH=x86_64 
> >>>
> >>> All warnings (new ones prefixed by >>):
> >>
> >> I'm sorry, what exactly does this mean?
> > sorry that the script has issue to provide empty warnings here, which
> > was supposed to list warnings with >> added to new ones like below.
> > 
> >    In file included from kernel//bpf/core.c:29:0:
> >>> include/linux/bpf.h:72:8: error: duplicate member 'security'
> >      void *security;
> >            ^
> > 
> > We will follow up to check what goes wrong.
> 
> Certainly odd, even in that tree/commit/header [0] I cannot see a duplicate
> security member in struct bpf_map.
that is one example i try to show what looks like for the >> prefix, and i copy
it from https://lists.01.org/pipermail/kbuild-all/2018-February/042706.html, which
is not for vhost repo.

Here for this report, the issue is as title "Warning: arch/x86/tools/test_get_len found difference at <pm_restore_gfp_mask>:ffffffff811aa5f0".

> 
>   [0] https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/tree/include/linux/bpf.h?h=vhost&id=cc1d1dc07885803981520a5303ef5b130f2ca2e8#n45

  reply	other threads:[~2018-02-08  0:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07  7:02 [vhost:vhost 19/20] Warning: arch/x86/tools/test_get_len found difference at <pm_restore_gfp_mask>:ffffffff811aa5f0 kbuild test robot
2018-02-08  0:09 ` Michael S. Tsirkin
2018-02-08  0:20   ` [kbuild-all] " Philip Li
2018-02-08  0:25     ` Daniel Borkmann
2018-02-08  0:37       ` Philip Li [this message]
2018-02-08  0:41         ` Daniel Borkmann

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=20180208003733.GA25579@intel.com \
    --to=philip.li@intel.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=liang.z.li@intel.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wei.w.wang@intel.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).