[lkml]   [2018]   [Jul]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH 0/2] Secure deletion under JFFS2
Security certifications such as FIPS require the capability to securely 
delete files, which is problematic under JFFS2's log-based model. We can
ensure that all dirty or obsolete data has been cleared at the conclusion
of secure deletion by forcibly driving the existing garbage collection
system however.

To that end, these patches provide two pieces of functionality:
1. -POLL signal handling in jffs2_gc to force complete collection of
dirty blocks up to the time it was started.
2. Synchronisation with userspace (via debugfs files) to allow
secure deletion to wait until that process has completed.

Theuns Verwoerd (2):
jffs2: Provide forced dirty node cleanup via POLL signal
jffs2: Provide jffs2_sync files to track gc POLL progress

fs/jffs2/Kconfig | 8 ++++++++
fs/jffs2/background.c | 31 ++++++++++++++++++++++++++++++-
fs/jffs2/build.c | 1 +
fs/jffs2/jffs2_fs_sb.h | 2 ++
fs/jffs2/nodelist.h | 1 +
fs/jffs2/nodemgmt.c | 6 +++++-
fs/jffs2/super.c | 40 ++++++++++++++++++++++++++++++++++++++++
7 files changed, 87 insertions(+), 2 deletions(-)


 \ /
  Last update: 2018-07-20 01:51    [W:0.117 / U:0.920 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site