linux-kernel - Re: [RFC] DMA mapping error check analysis

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1347290775.3071.1.camel@lorien2>
Date:	Mon, 10 Sep 2012 09:26:15 -0600
From:	Shuah Khan <shuah.khan@...com>
To:	Clemens Ladisch <clemens@...isch.de>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux1394-devel@...ts.sf.net,
	shuahkhan@...il.com
Subject: Re: [RFC] DMA mapping error check analysis


> >
> > http://linuxdriverproject.org/mediawiki/index.php/DMA_Mapping_Error_Analysis
> 
> > File Name                  # of calls  Status 	
> > drivers/firewire/core-iso.c   1        Unmap Broken
> > drivers/firewire/ohci.c       1        Unmap Broken
> 
> In ohci.c, ar_context_release() takes care of cleanup.
> 
> In core-iso.c, on failure, the callers are responsible to call
> fw_iso_buffer_destroy() eventually.  (ioctl_create_iso_context()
> doesn't do this correctly if it's called multiple times.)
> 

Thanks. I updated the page with your comments. I moved ohci.c to Good
status and left core-iso.c in Unmap Broken in case
ioctl_create_iso_context() case is worth fixing.

-- 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/