summaryrefslogtreecommitdiff
path: root/drivers/md/dm-unstripe.c
diff options
context:
space:
mode:
authorTushar Sugandhi <tusharsu@linux.microsoft.com>2021-07-13 03:48:59 +0300
committerMike Snitzer <snitzer@redhat.com>2021-08-10 20:34:22 +0300
commit8eb6fab402e23ae5de216c327fcd0dd6b54e135d (patch)
tree420b60941fd8693df9b2a177efb33dbb4df7babf /drivers/md/dm-unstripe.c
parent91ccbbac1747eea155632a1c6bb100052309b215 (diff)
downloadlinux-8eb6fab402e23ae5de216c327fcd0dd6b54e135d.tar.xz
dm ima: measure data on device resume
A given block device can load a table multiple times, with different input parameters, before eventually resuming it. Further, a device may be suspended and then resumed. The device may never resume after a table-load. Because of the above valid scenarios for a given device, it is important to measure and log the device resume event using IMA. Also, if the table is large, measuring it in clear-text each time the device changes state, will unnecessarily increase the size of IMA log. Since the table clear-text is already measured during table-load event, measuring the hash during resume should be sufficient to validate the table contents. Measure the device parameters, and hash of the active table, when the device is resumed. Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/md/dm-unstripe.c')
0 files changed, 0 insertions, 0 deletions