Re: [RFC] fsfreeze: moving from uniterruptible to killable

2013-03-27 Thread Marco Stornelli
2013/3/27 Jan Kara : > On Wed 27-03-13 12:39:10, Marco Stornelli wrote: >> 2013/3/26 Jan Kara : >> > On Sun 24-03-13 10:10:59, Marco Stornelli wrote: >> >> When a fs is frozen, a process can hang because we wait in >> >> uniterruptible state. We give the user the possibility to kill the >> >> proc

Re: [RFC] fsfreeze: moving from uniterruptible to killable

2013-03-27 Thread Jan Kara
On Wed 27-03-13 12:39:10, Marco Stornelli wrote: > 2013/3/26 Jan Kara : > > On Sun 24-03-13 10:10:59, Marco Stornelli wrote: > >> When a fs is frozen, a process can hang because we wait in > >> uniterruptible state. We give the user the possibility to kill the process. > > Yes, but it needs sligh

Re: [RFC] fsfreeze: moving from uniterruptible to killable

2013-03-27 Thread Marco Stornelli
2013/3/26 Jan Kara : > On Sun 24-03-13 10:10:59, Marco Stornelli wrote: >> When a fs is frozen, a process can hang because we wait in >> uniterruptible state. We give the user the possibility to kill the process. > Yes, but it needs slightly more work as you probably know... (bailing out > proper

Re: [RFC] fsfreeze: moving from uniterruptible to killable

2013-03-26 Thread Jan Kara
On Sun 24-03-13 10:10:59, Marco Stornelli wrote: > When a fs is frozen, a process can hang because we wait in > uniterruptible state. We give the user the possibility to kill the process. Yes, but it needs slightly more work as you probably know... (bailing out properly when the signal arrives).

[RFC] fsfreeze: moving from uniterruptible to killable

2013-03-24 Thread Marco Stornelli
When a fs is frozen, a process can hang because we wait in uniterruptible state. We give the user the possibility to kill the process. Not-signed-off-by: Marco Stornelli --- --- fs/super.c.orig 2013-03-24 09:56:33.0 +0100 +++ fs/super.c 2013-03-24 09:58:41.0 +0100 @@ -1198,7