From: Liam Mark <lmark@codeaurora.org>
To: Laura Abbott <labbott@redhat.com>
Cc: devel@driverdev.osuosl.org, linaro-mm-sig@lists.linaro.org,
Sumit Semwal <sumit.semwal@linaro.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: android: ion: Initialize dma_address of new sg list
Date: Fri, 16 Feb 2018 09:45:28 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1802160945020.20374@lmark-linux.qualcomm.com> (raw)
In-Reply-To: <9aa626cf-c122-55af-0c95-a9e9c12c6f19@redhat.com>
On Thu, 15 Feb 2018, Laura Abbott wrote:
> On 02/12/2018 01:25 PM, Liam Mark wrote:
> >
> > On Mon, 12 Feb 2018, Dan Carpenter wrote:
> >
> > > On Fri, Feb 09, 2018 at 10:16:56PM -0800, Liam Mark wrote:
> > > > Fix the dup_sg_table function to initialize the dma_address of the new
> > > > sg list entries instead of the source dma_address entries.
> > > >
> > > > Fixes: 17fd283f3870 ("staging: android: ion: Duplicate sg_table")
> > > > Signed-off-by: Liam Mark <lmark@codeaurora.org>
> > >
> > > How did you find this bug? What are the user visible effects of this
> > > bug? I'm probably going to ask you to send a v2 patch with a new
> > > changelog depending on the answers to these questions.
> >
> > I noticed the bug when reading through the code, I haven?t seen any
> > visible effects of this bug.
> >
> > From looking at the code I don?t see any obvious ways that this bug
> would
> > introduce any issues with the current code base.
> >
> > Liam
> >
>
> Given the way we duplicate the sg_list this should be harmless but you
> are right it's cleaner if we initialize the new list. You can add my
> Ack when you update with a new change log clarifying this.
>
> Thanks,
> Laura
>
Will do.
Thanks,
Liam
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-02-16 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 6:16 Liam Mark
2018-02-12 6:56 ` Dan Carpenter
2018-02-12 21:25 ` Liam Mark
2018-02-15 23:31 ` Laura Abbott
2018-02-16 17:45 ` Liam Mark [this message]
2018-02-16 16:23 ` Greg KH
2018-02-16 17:57 ` Liam Mark
2018-02-16 18:50 ` Greg KH
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=alpine.DEB.2.02.1802160945020.20374@lmark-linux.qualcomm.com \
--to=lmark@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.semwal@linaro.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
Powered by JetHome