https://bugzilla.kernel.org/show_bug.cgi?id=92271 --- Comment #7 from Alexander Holler <holler@xxxxxxxxxxxxx> --- The problem is the missing promise from the FS that is has overwritten the used blocks. Even using fstrim --secure doesn't give that promise, because the user doesn't know if the FS has given the blocks back to the device (as free). And as long as the FS doesn't give such a promise, the only way for the user to be sure is to shred the whole device/partition. So in case of ext4, implementing a syscall like s[ecure_]unlink() doesn't seem to be a big complicated thing and would be a very great start in solving the problem. Of course that might not be final ultimate solution because it doesn't solve the problem about what happens when files have been modified, moved and then deleted. Here something like the 's' bit could help. But I'm a friend of starting with small steps and I think a special unlink syscall would be a great and already useable start in solving the problem. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
