| 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
| ||
|
Date: Thu, 7 Jun 2007 12:45:07 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Chuck Ebbert <cebbert@...hat.com> Cc: Mark Lord <lkml@....ca>, Stephen Tweedie <sct@...hat.com>, "Theodore Ts'o" <tytso@....edu>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: ext3fs: umount+sync not enough to guarantee metadata-on-disk On Thu, 07 Jun 2007 12:11:58 -0400 Chuck Ebbert <cebbert@...hat.com> wrote: > On 06/07/2007 11:41 AM, Andrew Morton wrote: > >> mount /var/lib/mythtv -oremount,ro > >> sync > >> umount /var/lib/mythtv > > > > Did this succeed? If the application is still truncating that file, the > > umount should have failed. > > Shouldn't sync should wait for truncate to finish? I can't think of anything in there at present which would cause that to happen, and it's not immediately obvious how we _could_ make it happen - we have an inode which potentially has no dirty pages and which is itself clean. The truncate can span multiple journal commits, so forcing a journal commit in sync() won't necessarily block behind the truncate. I guess we could ask sync to speculatively take and release every inode's i_mutex or something. But even that would involve quite some hoop-jumping due to those infuriating spinlock-protected list_heads on the superblock. hmm. - 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