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] [thread-next>] [day] [month] [year] [list]
Message-Id: <88E7CDF01964465CB9F33DE11298271D@nsl.ad.nec.co.jp>
Date:	Mon, 14 Jul 2008 22:12:51 +0900
From:	"Takashi Sato" <t-sato@...jp.nec.com>
To:	"jim owens" <jowens@...com>
Cc:	<mtk.manpages@...glemail.com>, <axboe@...nel.dk>,
	<linux-kernel@...r.kernel.org>, <dm-devel@...hat.com>,
	<xfs@....sgi.com>, <linux-ext4@...r.kernel.org>,
	<viro@...IV.linux.org.uk>, <akpm@...ux-foundation.org>,
	<pavel@...e.cz>, <linux-fsdevel@...r.kernel.org>,
	<hch@...radead.org>, "Miklos Szeredi" <miklos@...redi.hu>,
	"Arjan van de Ven" <arjan@...radead.org>,
	"Theodore Tso" <tytso@....edu>,
	"Dave Chinner" <david@...morbit.com>
Subject: Re: [PATCH 3/3] Add timeout feature

Hi,

jim owens wrote:
> In addition to the user controllable timeout mechanism,
> we internally implement AUTO-THAW in the filesystem
> whenever necessary to prevent a kernel hang/crash.
>
> If an AUTO-THAW occurs, we post to the log and an
> event manager so the user knows the snapshot is bad.

I am interested in AUTO-THAW.
What is the difference between the timeout and AUTO-THAW?
When the kernel detects a deadlock, does it occur to solve it?

Cheers, Takashi
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ