diff options
| author | Sami Tolvanen <samitolvanen@google.com> | 2014-12-18 16:15:30 +0000 |
|---|---|---|
| committer | Sami Tolvanen <samitolvanen@google.com> | 2015-02-27 11:28:34 +0000 |
| commit | 214f33b8c095feedfdbaa680ff6ffb763f47d375 (patch) | |
| tree | f840f0deeaebc0a53ce6612106eed82b7ddcacdc /fs_mgr/fs_mgr_priv.h | |
| parent | be9712156bdcf8cff774a78a3afdb0c562998c73 (diff) | |
| download | system_core-214f33b8c095feedfdbaa680ff6ffb763f47d375.zip system_core-214f33b8c095feedfdbaa680ff6ffb763f47d375.tar.gz system_core-214f33b8c095feedfdbaa680ff6ffb763f47d375.tar.bz2 | |
Set underlying block device RO when enabling verity
Currently, when verity is set up on a block device, the underlying
device is still accessible directly. Change the existing function
fs_set_blk_ro visible to other fs_mgr modules, change the behavior
to match the comment above the function definition, and call it to
disable write access to the block device when setting up verity.
Bug: 18609347
Change-Id: I7884175df15f9161174788d74d20a08e4cd472ca
Diffstat (limited to 'fs_mgr/fs_mgr_priv.h')
| -rw-r--r-- | fs_mgr/fs_mgr_priv.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs_mgr/fs_mgr_priv.h b/fs_mgr/fs_mgr_priv.h index 4ba6f92..88a1040 100644 --- a/fs_mgr/fs_mgr_priv.h +++ b/fs_mgr/fs_mgr_priv.h @@ -79,5 +79,7 @@ #define DM_BUF_SIZE 4096 +int fs_mgr_set_blk_ro(const char *blockdev); + #endif /* __CORE_FS_MGR_PRIV_H */ |