public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xen.org, linux-kernel@vger.kernel.org,
	jgross@suse.com, Stefano Stabellini <stefano@aporeto.com>
Subject: Re: [PATCH v7 13/13] xen: introduce a Kconfig option to enable the pvcalls frontend
Date: Mon, 30 Oct 2017 16:00:31 -0400	[thread overview]
Message-ID: <f87b959d-e820-1b33-bd49-7e237281bd8b@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1710301231480.7297@sstabellini-ThinkPad-X260>

On 10/30/2017 03:48 PM, Stefano Stabellini wrote:
> On Mon, 30 Oct 2017, Boris Ostrovsky wrote:
>>
>> Build warnings (gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1))
> Hi Boris, I am trying to repro the warnings below. I have been
> unsuccessful so far. What system are you using? Fedora? CentOS? Do have
> any specific CFLAGS settings?


I am on Fedora24, nothing interesting in my environment. For example,

ostr@workbase> env | grep FLAGS
ostr@workbase>

I'll send you my config file in a separate email, just in case.  Your
patches are on top of

    0b07194 Linux 4.14-rc7

ostr@workbase> gcc -Wp,-MD,drivers/xen/.pvcalls-front.o.d  -nostdinc
-isystem /usr/lib/gcc/x86_64-redhat-linux/6.3.1/include
-I/data/upstream/linux-xen/arch/x86/include
-I./arch/x86/include/generated  -I/data/upstream/linux-xen/include
-I./include -I/data/upstream/linux-xen/arch/x86/include/uapi
-I./arch/x86/include/generated/uapi
-I/data/upstream/linux-xen/include/uapi -I./include/generated/uapi
-include /data/upstream/linux-xen/include/linux/kconfig.h 
-I/data/upstream/linux-xen/drivers/xen -Idrivers/xen -D__KERNEL__ -Wall
-Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -fshort-wchar -Werror-implicit-function-declaration
-Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2
-mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup
-mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time
-DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
-DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1
-DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1
-DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe
-Wno-sign-compare -fno-asynchronous-unwind-tables
-fno-delete-null-pointer-checks -Wno-frame-address -O2
--param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO
-Wframe-larger-than=2048 -fstack-protector-strong
-Wno-unused-but-set-variable -Wno-unused-const-variable
-fno-omit-frame-pointer -fno-optimize-sibling-calls
-fno-var-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY
-Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow
-fconserve-stack -Werror=implicit-int -Werror=strict-prototypes
-Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init  -DMODULE  -DKBUILD_BASENAME='"pvcalls_front"' 
-DKBUILD_MODNAME='"pvcalls_front"' -c -o drivers/xen/pvcalls-front.o
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c: In function
‘__write_ring’:
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:459:3: warning:
ignoring return value of ‘copy_from_iter’, declared with attribute
warn_unused_result [-Wunused-result]
   copy_from_iter(data->out + masked_prod, len, msg_iter);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:462:4: warning:
ignoring return value of ‘copy_from_iter’, declared with attribute
warn_unused_result [-Wunused-result]
    copy_from_iter(data->out + masked_prod,
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            array_size - masked_prod, msg_iter);
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:464:4: warning:
ignoring return value of ‘copy_from_iter’, declared with attribute
warn_unused_result [-Wunused-result]
    copy_from_iter(data->out,
    ^~~~~~~~~~~~~~~~~~~~~~~~~
            len - (array_size - masked_prod),
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            msg_iter);
            ~~~~~~~~~
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:468:4: warning:
ignoring return value of ‘copy_from_iter’, declared with attribute
warn_unused_result [-Wunused-result]
    copy_from_iter(data->out + masked_prod, len, msg_iter);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c: In function
‘__read_ring’:
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:560:3: warning:
ignoring return value of ‘copy_to_iter’, declared with attribute
warn_unused_result [-Wunused-result]
   copy_to_iter(data->in + masked_cons, len, msg_iter);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:563:4: warning:
ignoring return value of ‘copy_to_iter’, declared with attribute
warn_unused_result [-Wunused-result]
    copy_to_iter(data->in + masked_cons,
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          array_size - masked_cons, msg_iter);
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:565:4: warning:
ignoring return value of ‘copy_to_iter’, declared with attribute
warn_unused_result [-Wunused-result]
    copy_to_iter(data->in,
    ^~~~~~~~~~~~~~~~~~~~~~
          len - (array_size - masked_cons),
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          msg_iter);
          ~~~~~~~~~
/data/upstream/linux-xen/drivers/xen/pvcalls-front.c:569:4: warning:
ignoring return value of ‘copy_to_iter’, declared with attribute
warn_unused_result [-Wunused-result]
    copy_to_iter(data->in + masked_cons, len, msg_iter);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ostr@workbase>

  reply	other threads:[~2017-10-30 19:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 19:11 [PATCH v7 00/13] introduce the Xen PV Calls frontend Stefano Stabellini
2017-10-26 19:11 ` [PATCH v7 01/13] xen/pvcalls: introduce the pvcalls xenbus frontend Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 02/13] xen/pvcalls: implement frontend disconnect Stefano Stabellini
2017-10-26 19:42     ` Boris Ostrovsky
2017-10-26 19:11   ` [PATCH v7 03/13] xen/pvcalls: connect to the backend Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 04/13] xen/pvcalls: implement socket command and handle events Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 05/13] xen/pvcalls: implement connect command Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 06/13] xen/pvcalls: implement bind command Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 07/13] xen/pvcalls: implement listen command Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 08/13] xen/pvcalls: implement accept command Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 09/13] xen/pvcalls: implement sendmsg Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 10/13] xen/pvcalls: implement recvmsg Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 11/13] xen/pvcalls: implement poll command Stefano Stabellini
2017-10-26 19:11   ` [PATCH v7 12/13] xen/pvcalls: implement release command Stefano Stabellini
2017-10-26 19:49     ` Boris Ostrovsky
2017-10-26 19:11   ` [PATCH v7 13/13] xen: introduce a Kconfig option to enable the pvcalls frontend Stefano Stabellini
2017-10-26 19:52     ` Boris Ostrovsky
2017-10-26 20:16       ` Stefano Stabellini
2017-10-26 20:45         ` Boris Ostrovsky
2017-10-26 20:49           ` Stefano Stabellini
2017-10-26 20:56             ` Boris Ostrovsky
2017-10-30 15:22           ` Boris Ostrovsky
2017-10-30 19:48             ` Stefano Stabellini
2017-10-30 20:00               ` Boris Ostrovsky [this message]
2017-10-30 21:42                 ` Stefano Stabellini
2017-10-30 22:02                   ` Boris Ostrovsky
2017-10-30 22:14                     ` Stefano Stabellini

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=f87b959d-e820-1b33-bd49-7e237281bd8b@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=stefano@aporeto.com \
    --cc=xen-devel@lists.xen.org \
    /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