From: kbuild test robot <lkp@intel.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: kbuild-all@01.org, kys@microsoft.com, haiyangz@microsoft.com,
linux-kernel@vger.kernel.org, Olaf Hering <olaf@aepfle.de>
Subject: [PATCH] hv: util: fix memdup_user.cocci warnings
Date: Wed, 30 Sep 2015 17:25:29 +0800 [thread overview]
Message-ID: <20150930092529.GA121674@lkp-sb04> (raw)
In-Reply-To: <1443603911-25696-1-git-send-email-olaf@aepfle.de>
drivers/hv/hv_utils_transport.c:83:9-16: 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: Olaf Hering <olaf@aepfle.de>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
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)
) || ...)
next prev parent reply other threads:[~2015-09-30 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 9:05 [PATCH] hv: util: catch allocation errors Olaf Hering
2015-09-30 9:25 ` kbuild test robot [this message]
2015-09-30 9:25 ` kbuild test robot
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=20150930092529.GA121674@lkp-sb04 \
--to=lkp@intel.com \
--cc=haiyangz@microsoft.com \
--cc=kbuild-all@01.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
all inboxes | Powered by JetHome®