From: kbuild test robot <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Ivan Hu <ivan.hu-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Matt Fleming
<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
Subject: [PATCH] efi: fix memdup_user.cocci warnings
Date: Tue, 6 Sep 2016 02:18:43 +0800 [thread overview]
Message-ID: <20160905181843.GA24024@lkp-ne04> (raw)
In-Reply-To: <201609060241.wcHLKv2z%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
drivers/firmware/efi/test/efi_test.c:269:8-15: WARNING opportunity for memdup_user
Use memdup_user rather than duplicating its implementation
This is a little bit restricted to reduce false positives
Generated by: scripts/coccinelle/api/memdup_user.cocci
CC: Ivan Hu <ivan.hu-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Signed-off-by: Fengguang Wu <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
---
0 files changed
rule starting on line 17: position variables or mixed modifs interfere with comm_assoc isobool (
(
(
(unknown *to == NULL)
>>> IS_ERR(rule starting on line 17:to)
|
!unknown *to
>>> IS_ERR(rule starting on line 17:to)
)
|
(unknown *NULL == unknown *to)
>>> IS_ERR(rule starting on line 17:to)
) || ...)
prev parent reply other threads:[~2016-09-05 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 18:18 [efi:next 25/27] drivers/firmware/efi/test/efi_test.c:269:8-15: WARNING opportunity for memdup_user kbuild test robot
[not found] ` <201609060241.wcHLKv2z%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-09-05 18:18 ` kbuild test robot [this message]
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=20160905181843.GA24024@lkp-ne04 \
--to=fengguang.wu-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=ivan.hu-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.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