Hi, after some comments, I changed the scope of the patch series. As Al said the call of freezing are too deep in the call chain and to avoid several headaches it's better to manage an interruption by sigkill only when the call are enough "near" to the user space. About the pagefault: actually the return VM_FAULT_RETRY from page_mkwrite it seems possible but it can create some problem to the callers. Inside page_mkwrite we should check if the caller has set FAULT_FLAG_ALLOW_RETRY but this flag is not passed to the page_mkwrite callback, any tips about this point? Marco Stornelli (2): fsfreeze: add new internal __sb_start_write_wait fsfreeze: replace sb_start_write with sb_start_write_killable fs/btrfs/file.c | 4 +++- fs/cifs/file.c | 4 +++- fs/fuse/file.c | 4 +++- fs/ntfs/file.c | 4 +++- fs/ocfs2/file.c | 4 +++- fs/open.c | 8 ++++++-- fs/splice.c | 4 +++- fs/super.c | 47 ++++++++++++++++++++++++++++++++++++++++------- fs/xfs/xfs_file.c | 4 +++- include/linux/fs.h | 23 ++++++++++++++++++----- mm/filemap.c | 4 +++- mm/filemap_xip.c | 4 +++- 12 files changed, 91 insertions(+), 23 deletions(-) -- 1.7.3.4 --- -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
