[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1347036869.2603.28.camel@lorien2>
Date: Fri, 07 Sep 2012 10:54:29 -0600
From: Shuah Khan <shuah.khan@...com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: fujita.tomonori@....ntt.co.jp,
Andrew Morton <akpm@...ux-foundation.org>,
paul.gortmaker@...driver.com, bhelgaas@...gle.com,
amwang@...hat.com, joerg.roedel@....com, kubakici@...pl,
dan.carpenter@...cle.com,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
LKML <linux-kernel@...r.kernel.org>,
devel@...uxdriverproject.org, shuahkhan@...il.com
Subject: Re: [RFC] DMA mapping error check analysis
On Fri, 2012-09-07 at 12:20 -0400, Alan Stern wrote:
> On Fri, 7 Sep 2012, Shuah Khan wrote:
>
> > I analyzed all calls to dma_map_single() and dma_map_page() in the
> > kernel, to see if callers check for mapping errors, before using the
> > returned address.
> >
> > The goal of this analysis is to find drivers that currently do not
> > check dma mapping errors, and fix them.
> >
> > I documented the results of this analysis:
> >
> > http://linuxdriverproject.org/mediawiki/index.php/DMA_Mapping_Error_Analysis
> >
> > Please review and give me feedback on the analysis and the proposed
> > next steps.
>
> Your first table (dma_map_single) lists drivers/usb/core/usb.c and
> marks it as Bad. This is a mistake because the code is #ifdef'ed out.
> It hasn't been used in many years; it should be removed.
Thanks for catching it. I did note that in my research notes and that
was left out by mistake when I put the table together. Table is updated
now with your comment and marked it a Cleanup item.
-- Shuah
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists