Cc: <alan@...>, <andi@...>, Arjan van de Ven <arjan@...>, Eric Paris <eparis@...>, <hch@...>, <linux-kernel@...>, <malware-list@...>, <malware-list-bounces@...>, <peterz@...>, <viro@...>
So in essence, what I hear you saying is that all AV products want to
work in a mode where the moment the inode falls out of the inode
cache, and we lose the "clean" bit, when the inode is brought back
into the cache, it will be scanned again. That is, the "clean" bit is
never persistent, and never needs to be stored in memory.
That seems fair; if it turns out there is an AV product that wants to
optimize this a bit further, as long as we provide a persistent inode
version/generation number, they can always do their own persistent
database in userspace.
- Ted
--
