From: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org, anton@samba.org
Subject: Re: [PATCH] ppc/iommu: prevent false TCE leak message
Date: Fri, 28 Dec 2012 14:55:04 -0200 [thread overview]
Message-ID: <20121228165504.GC21831@oc0268524204.ibm.com> (raw)
In-Reply-To: <20121228052135.GB9975@shangw.(null)>
On Fri, Dec 28, 2012 at 01:21:35PM +0800, Gavin Shan wrote:
> On Thu, Dec 27, 2012 at 02:28:06PM -0200, Thadeu Lima de Souza Cascardo wrote:
> >When a device DMA window includes the address 0, it's reserved in the
> >TCE bitmap to avoid returning that address to drivers.
> >
> >When the device is removed, the bitmap is checked for any mappings not
> >removed by the driver, indicating a possible DMA mapping leak. Since the
> >reserved address is not cleared, a message is printed, warning of such a
> >leak.
> >
> >Check for the reservation, and clear it before checking for any other
> >standing mappings.
> >
> >Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
> >---
> > arch/powerpc/kernel/iommu.c | 5 +++++
> > 1 files changed, 5 insertions(+), 0 deletions(-)
> >
> >diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c
> >index 8226c6c..226e9e5 100644
> >--- a/arch/powerpc/kernel/iommu.c
> >+++ b/arch/powerpc/kernel/iommu.c
> >@@ -717,6 +717,11 @@ void iommu_free_table(struct iommu_table *tbl, const char *node_name)
> > return;
> > }
> >
> >+ /* In case we have reserved the first bit, we should not emit
> >+ * the warning below. */
>
> At least, the comment would look like:
>
> /*
> * xxxxxxx
> */
>
Sure. New code should always follow coding style. :-)
How do you suggest merging with the comment below? I think it's closer
to the code it comments about, so I'd rather keep it where it is.
> >+ if (tbl->it_offset == 0)
> >+ clear_bit(0, tbl->it_map);
> >+
> > /* verify that table contains no entries */
> > /* it_size is in entries, and we're examining 64 at a time */
>
> The comment would be merged as well? :-)
>
I also considered replacing this code by this:
/* verify that table contains no entries */
- /* it_size is in entries, and we're examining 64 at a time */
- for (i = 0; i < (tbl->it_size/64); i++) {
- if (tbl->it_map[i] != 0) {
+ if (find_first_bit(tbl->it_map, tbl->it_size) < tbl->it_size)
printk(KERN_WARNING "%s: Unexpected TCEs for
%s\n",
__func__, node_name);
- break;
- }
- }
I'll resend the "unreserving" patch with the fixed comment styling, but
without merging comments. And I will send this other patch for comments.
Regards.
Thadeu Cascardo.
> > for (i = 0; i < (tbl->it_size/64); i++) {
>
> Thanks,
> Gavin
next prev parent reply other threads:[~2012-12-28 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 16:28 [PATCH] ppc/iommu: prevent false TCE leak message Thadeu Lima de Souza Cascardo
2012-12-28 5:21 ` Gavin Shan
2012-12-28 16:55 ` Thadeu Lima de Souza Cascardo [this message]
2012-12-28 19:08 ` [PATCH 1/2] " Thadeu Lima de Souza Cascardo
2012-12-28 19:08 ` [PATCH 2/2] ppc/iommu: use find_first_bit to look up entries in the iommu table Thadeu Lima de Souza Cascardo
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=20121228165504.GC21831@oc0268524204.ibm.com \
--to=cascardo@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=shangw@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).