[RFC PATCH 3/3] fs: detect that the i_rwsem has already been taken exclusively
Mimi Zohar
zohar at linux.vnet.ibm.com
Mon Oct 2 12:25:09 UTC 2017
On Sun, 2017-10-01 at 22:25 -0500, Eric W. Biederman wrote:
> Mimi Zohar <zohar at linux.vnet.ibm.com> writes:
> > There should be no open writers in ima_check_last_writer(), so the
> > file shouldn't be changing.
>
> This is slightly tangential but I think important to consider.
> What do you do about distributed filesystems fuse, nfs, etc that
> can change the data behind the kernels back.
Exactly!
> Do you not support such systems or do you have a sufficient way to
> detect changes?
Currently, only the initial file access in policy is measured,
verified, audited. Even if there was a way of detecting the change,
since we can't trust these file systems, the performance would be
awful, but we should probably not be caching the
measurement/verification results.
Mimi
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the Linux-security-module-archive
mailing list