From: Michal Hocko <mhocko@kernel.org>
To: "Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kmemcheck: correctly remove kmemcheck call from dma_map_sg_attrs
Date: Fri, 13 Oct 2017 09:11:21 +0200 [thread overview]
Message-ID: <20171013071121.4v73j7gn472ezv23@dhcp22.suse.cz> (raw)
In-Reply-To: <20171012192151.26531-1-alexander.levin@verizon.com>
On Thu 12-10-17 19:22:05, Sasha Levin wrote:
> We have missed removing some code as part of removing the kmemcheck
> hooks.
>
> Unfourtenatly this got missed during my review, and the code was
> still building.
>
> Reported-by: Michal Hocko <mhocko@kernel.org>
> Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Yes this would be the proper fix for the specific issue I have noticed.
There might be others I haven't even checked. Really the only way to
make this chage is to post a reproducible steps to regenerate your diff
and review that the used scripts are correct. Follow up fixes are not a
way to go
> ---
> include/linux/dma-mapping.h | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
> index 83f3ab31efc4..2911389bc147 100644
> --- a/include/linux/dma-mapping.h
> +++ b/include/linux/dma-mapping.h
> @@ -260,10 +260,8 @@ static inline int dma_map_sg_attrs(struct device *dev, struct scatterlist *sg,
> unsigned long attrs)
> {
> const struct dma_map_ops *ops = get_dma_ops(dev);
> - int i, ents;
> - struct scatterlist *s;
> + int ents;
>
> - for_each_sg(sg, s, nents, i)
> BUG_ON(!valid_dma_direction(dir));
> ents = ops->map_sg(dev, sg, nents, dir, attrs);
> BUG_ON(ents < 0);
> --
> 2.11.0
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-10-13 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 19:22 Levin, Alexander (Sasha Levin)
2017-10-13 7:11 ` Michal Hocko [this message]
2017-10-13 14:05 ` Levin, Alexander (Sasha Levin)
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=20171013071121.4v73j7gn472ezv23@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®