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
| ||
|
Date: Tue, 28 Dec 2010 16:48:46 +0200 From: Ohad Ben-Cohen <ohad@...ery.com> To: Felipe Contreras <felipe.contreras@...il.com> Cc: Felipe Contreras <felipe.contreras@...ia.com>, linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org, greg@...ah.com, omar.ramirez@...com, fernando.lugo@...com, nm@...com, ameya.palande@...ia.com, h-kanigeri2@...com Subject: Re: [PATCH v2] staging: tidspbridge: protect dmm_map properly On Tue, Dec 28, 2010 at 2:12 PM, Felipe Contreras <felipe.contreras@...il.com> wrote: > On Tue, Dec 28, 2010 at 12:56 PM, Ohad Ben-Cohen <ohad@...ery.com> wrote: >> I still don't know how exactly you triggered the bug: is gst-dsp >> multithreaded ? and one of its threads invoked proc_un_map() while >> another thread called proc_begin_dma() ? > > I haven't investigated why that happens Btw, I still think you should look into this. The kernel panic will be solved, but you may still have a race there that can lead to data corruption: if proc_un_map will be fast enough, it will acquire the proc_lock mutex before proc_begin_dma(), and then you will miss a cache operation. -- 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