[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080815150509.20ffb91d@infradead.org>
Date: Fri, 15 Aug 2008 15:05:09 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Jan Harkes <jaharkes@...cmu.edu>
Cc: Rik van Riel <riel@...hat.com>,
"Press, Jonathan" <Jonathan.Press@...com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Eric Paris <eparis@...hat.com>, peterz@...radead.org,
linux-kernel@...r.kernel.org, malware-list@...ts.printk.net,
hch@...radead.org, andi@...stfloor.org, viro@...IV.linux.org.uk
Subject: Re: [malware-list] TALPA - a threat model? well sorta.
On Fri, 15 Aug 2008 16:16:22 -0400
Jan Harkes <jaharkes@...cmu.edu> wrote:
> > I believe we really do need the block-on-open.
I believe more that we need block-on-read ;-)
(on open we can start an async scan to cut latency)
read() (or mmap etc) is where the actual use/transfer of
contaminated data happens, not in the open.
--
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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