Ok, I've update the secure delete patch to now check is_secure_delete(inode) to see if either the chattr +s bit is set, or if the superblock has EXT2FS_MOUNT_SECRM (which I've added) set. I believe I've correctly modified the super.c to support a "secrm" mount option, but I haven't tested it so I can't say for sure. That is to say it compiles, but I haven't tried to run it. This rev of the patch is to see if the direction (and logic) of the secure delete functionality is in line with what people are thinking. There is some complexity around directory files. If a directory file has chattr +s set, then any directory entry within that file will be erased when the entry is removed. If a file has chattr +s set, or the fs was mounted with SECRM then the directory entry is removed. I would like people to pay particular attention to this part of the patch, its the area I'm least confident with. A directory entry's rec_len is preserved, in case we are removing the first entry for a directory block. The rest of the patch is basicly unchanged from the previous patchs. I haven't done a patch for ext3, when this one is agreed on then I'll it port acroos to ext3. peace, --gq