linux-kernel - Re: XFS vs. swsusp

lists.openwall.net		lists / announce john-users owl-users popa3d-users / xvendor oss-security / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4
Open Source and information security mailing list archives

This website is powered by Openwall GNU/*/Linux security-enhanced OS

[<prev] [next>] [<thread-prev] [month] [year] [list]

Date:	Tue, 1 Aug 2006 02:47:21 +0200
From:	Pavel Machek <pavel@....cz>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: XFS vs. swsusp

Hi!

> > > timer driven wakeup done on the per-fs xfssyncd kernel threads,
> > > which do background metadata writeout and will write to the log
> > > periodically... but if those processes are all stopped too, you
> > > should be OK.
> > 
> > Timer only wakes up xfssyncd thread, right? That's okay, as that
> > thread will be stopped.
> 
> But we call sync() before kernel threads are frozen.  What happens if xfssyncd
> gets woken up by the timer after the sync() and before we freeze it?

xfssyncd writes some data to disk, but that is okay (no important data
could be generated in the meantime) and then it is frozen. As we take
system snapshot after the freeze, it is okay, because image is
consistent.

I do not see a problem.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/