From: lkp@intel.com (kbuild test robot)
Subject: [PATCH] lightnvm: fix memdup_user.cocci warnings
Date: Wed, 28 Oct 2015 00:15:54 +0800 [thread overview]
Message-ID: <20151027161554.GA3884@lkp-ib03> (raw)
In-Reply-To: <1445957719-5368-2-git-send-email-m@bjorling.me>
drivers/lightnvm/core.c:657: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: Matias Bj?rling <m at bjorling.me>
Signed-off-by: Fengguang Wu <fengguang.wu at 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-10-27 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 14:55 [PATCH v12 0/5] Support for Open-Channel SSDs Matias Bjørling
2015-10-27 14:55 ` [PATCH v12 1/5] lightnvm: " Matias Bjørling
2015-10-27 16:15 ` kbuild test robot
2015-10-27 16:15 ` kbuild test robot [this message]
2015-10-27 14:55 ` [PATCH v12 2/5] gennvm: Generic NVM manager Matias Bjørling
2015-10-27 20:43 ` kbuild test robot
2015-10-27 21:18 ` kbuild test robot
2015-10-27 14:55 ` [PATCH v12 3/5] rrpc: Round-robin sector target with cost-based gc Matias Bjørling
2015-10-27 23:44 ` kbuild test robot
2015-10-27 14:55 ` [PATCH v12 4/5] null_nvm: LightNVM test driver Matias Bjørling
2015-10-27 22:24 ` kbuild test robot
2015-10-27 14:55 ` [PATCH v12 5/5] nvme: LightNVM support Matias Bjørling
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=20151027161554.GA3884@lkp-ib03 \
--to=lkp@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