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
| ||
|
Message-ID: <20080709065758.4ac6b3c5@infradead.org> Date: Wed, 9 Jul 2008 06:57:58 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Olaf Frączyk <olaf@....poznan.pl> Cc: Theodore Tso <tytso@....edu>, Miklos Szeredi <miklos@...redi.hu>, hch@...radead.org, pavel@...e.cz, t-sato@...jp.nec.com, akpm@...ux-foundation.org, viro@...IV.linux.org.uk, linux-ext4@...r.kernel.org, xfs@....sgi.com, dm-devel@...hat.com, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, axboe@...nel.dk, mtk.manpages@...glemail.com Subject: Re: [PATCH 3/3] Add timeout feature On Wed, 09 Jul 2008 14:59:20 +0200 Olaf Frączyk <olaf@....poznan.pl> wrote: > On Wed, 2008-07-09 at 08:24 -0400, Theodore Tso wrote: > > On Wed, Jul 09, 2008 at 09:49:58PM +1000, Dave Chinner wrote: > > > (e) none of the above. The kernel compilation will appear to > > > pause until the filesystem is unfrozen. No other visible effect > > > should occur. It will get blocked in a write or filesystem > > > transaction because the fs is frozen. > > > > So if the process which froze the filesystem accidentally tries > > writing to a log file (or database file containing the backup > > information, or whatever) that happens to be on the filesystem that > > is frozen, that process will get blocked and you end up in a > > deadlock; did I get that right? > Where do you see the deadlock? > The process doesn't have a lock on filesystem or something. You can > always unfreeze from another process. > if it's one of your main filesystems... good luck starting a shell without writing a single thing to disk... FAIL. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists