public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>,
	Paul Mackerras <paulus@ozlabs.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warnings
Date: Tue, 2 May 2017 16:05:30 +1000	[thread overview]
Message-ID: <20170502160530.34b680b7@canb.auug.org.au> (raw)

Hi all,

The linux-next build (powerpc allyesconfig) produced these warnings
(and have for a while):

arch/powerpc/kvm/book3s_pr_papr.c: In function 'kvmppc_h_pr_enter':
arch/powerpc/kvm/book3s_pr_papr.c:53:2: warning: ignoring return value of 'copy_from_user', declared with attribute warn_unused_result [-Wunused-result]
  copy_from_user(pteg, (void __user *)pteg_addr, sizeof(pteg));
  ^
arch/powerpc/kvm/book3s_pr_papr.c:74:2: warning: ignoring return value of 'copy_to_user', declared with attribute warn_unused_result [-Wunused-result]
  copy_to_user((void __user *)pteg_addr, hpte, HPTE_SIZE);
  ^
arch/powerpc/kvm/book3s_pr_papr.c: In function 'kvmppc_h_pr_remove':
arch/powerpc/kvm/book3s_pr_papr.c:96:2: warning: ignoring return value of 'copy_from_user', declared with attribute warn_unused_result [-Wunused-result]
  copy_from_user(pte, (void __user *)pteg, sizeof(pte));
  ^
arch/powerpc/kvm/book3s_pr_papr.c:106:2: warning: ignoring return value of 'copy_to_user', declared with attribute warn_unused_result [-Wunused-result]
  copy_to_user((void __user *)pteg, &v, sizeof(v));
  ^
arch/powerpc/kvm/book3s_pr_papr.c: In function 'kvmppc_h_pr_protect':
arch/powerpc/kvm/book3s_pr_papr.c:214:2: warning: ignoring return value of 'copy_from_user', declared with attribute warn_unused_result [-Wunused-result]
  copy_from_user(pte, (void __user *)pteg, sizeof(pte));
  ^
arch/powerpc/kvm/book3s_pr_papr.c:237:2: warning: ignoring return value of 'copy_to_user', declared with attribute warn_unused_result [-Wunused-result]
  copy_to_user((void __user *)pteg, pte, sizeof(pte));
  ^
arch/powerpc/kvm/book3s_pr_papr.c: In function 'kvmppc_h_pr_bulk_remove':
arch/powerpc/kvm/book3s_pr_papr.c:174:3: warning: ignoring return value of 'copy_from_user', declared with attribute warn_unused_result [-Wunused-result]
   copy_from_user(pte, (void __user *)pteg, sizeof(pte));
   ^
arch/powerpc/kvm/book3s_pr_papr.c:187:4: warning: ignoring return value of 'copy_to_user', declared with attribute warn_unused_result [-Wunused-result]
    copy_to_user((void __user *)pteg, &v, sizeof(v));
    ^

These calls have been there since about v3.1-rc8.  I assume the
copy_to/from_user() work has pointed them out.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2017-05-02  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  6:05 Stephen Rothwell [this message]
2017-05-02  9:53 ` linux-next: build warnings Michael Ellerman
2017-05-02 11:17   ` Stephen Rothwell
2017-05-02 11:21     ` Stephen Rothwell
2017-05-02 12:46     ` Michael Ellerman

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=20170502160530.34b680b7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@ozlabs.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