RFC fsfreeze: from uninterruptible to killable
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 RFC Latest0 of 3 patches 0 repliesNew
- v2 RFC1 of 2 patches 1 replySuperseded
- v14 patches 7 repliesSuperseded
Patches in v3 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH 0/3 v3][RFC] fsfreeze: from uninterruptible to killable
Hi,
I rebased the work on top of -next and I applied a Jan's comment about __sb_start_write. I did some basic tests and they are ok.
Open points:
- without change mnt_want_write several paths are still blocking paths;
- page_mkwrite still call blocking variant of __sb_start_write.
Any comments are welcome.
Regards.
Marco Stornelli (3):
fsfreeze: wait in killable state in __sb_start_write
fsfreeze: added new file_start_write_killable
fsfreeze: use sb_start_write_killable instead of sb_start_write
drivers/block/loop.c | 4 +++- fs/aio.c | 7 +++++-- fs/coda/file.c | 4 +++- fs/open.c | 8 ++++++-- fs/read_write.c | 28 +++++++++++++++++----------- fs/splice.c | 4 +++- fs/super.c | 24 ++++++++++++++++++------ include/linux/fs.h | 36 ++++++++++++++++++++++++++++++------ 8 files changed, 85 insertions(+), 30 deletions(-)
Signature · 2 lines
1.7.3.4 ---