linux-kernel - [PATCH 0/3 v3][RFC] fsfreeze: from uninterruptible to killable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <516934C0.2080103@gmail.com>
Date:	Sat, 13 Apr 2013 12:34:40 +0200
From:	Marco Stornelli <marco.stornelli@...il.com>
To:	Linux FS Devel <linux-fsdevel@...r.kernel.org>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jan Kara <jack@...e.cz>, Al Viro <viro@...IV.linux.org.uk>
Subject: [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(-)

-- 
1.7.3.4
---

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/