linux-kernel - Re: [PATCH 0/4] fsfreeze: from uninterruptible to killable waiting

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130406152247.GJ4068@ZenIV.linux.org.uk>
Date:	Sat, 6 Apr 2013 16:22:48 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Marco Stornelli <marco.stornelli@...il.com>
Cc:	Linux FS Devel <linux-fsdevel@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 0/4] fsfreeze: from uninterruptible to killable waiting

On Sat, Apr 06, 2013 at 12:03:00PM +0200, Marco Stornelli wrote:
> Hi all,
> 
> with this patch series we try to change the fs freeze behavior in order
> to sleep in a killable state instead of sleeping in uninterruptible 
> state. The patches are *NOT* tested because but a first review is welcome.
> The design is simply:
> 
> 1) Internal fs operations are not changed from fsfreeze point of view, 
> sb_start_intwrite is not changed;
> 
> 2) sb_start_write and sb_start_pagefault now return a proper error code 
> if the process receive SIGKILL and all the functions must manage this 
> error and return EINTR or VM_FAULT_RETRY.

sb_start_write() is done _way_ too deep in the call chain in the mainline;
check the changes in -next, please.
--
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/