[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171003195930.ivgaccdabxczar62@thunk.org>
Date: Tue, 3 Oct 2017 15:59:30 -0400
From: Theodore Ts'o <tytso@....edu>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: viro@...iv.linux.org.uk, bart.vanassche@....com,
ming.lei@...hat.com, darrick.wong@...cle.com, jikos@...nel.org,
rjw@...ysocki.net, pavel@....cz, len.brown@...el.com,
linux-fsdevel@...r.kernel.org, boris.ostrovsky@...cle.com,
jgross@...e.com, todd.e.brandt@...ux.intel.com, nborisov@...e.com,
jack@...e.cz, martin.petersen@...cle.com, ONeukum@...e.com,
oleksandr@...alenko.name, oleg.b.antonyan@...il.com,
linux-pm@...r.kernel.org, linux-block@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 4/5] ext4: add fs freezing support on suspend/hibernation
On Tue, Oct 03, 2017 at 11:53:12AM -0700, Luis R. Rodriguez wrote:
> @@ -4926,7 +4926,7 @@ static int ext4_unfreeze(struct super_block *sb)
> ext4_set_feature_journal_needs_recovery(sb);
> }
>
> - ext4_commit_super(sb, 1);
> + ext4_commit_super(sb, 0);
> return 0;
> }
>
After we remove add the NEEDS_RECOVERY flag, we need to make sure
recovery flag is pushed out to disk before any other changes are
allowed to be pushed out to disk. That's why we originally did the
update synchronously.
There are other ways we could fulfill this requirements, but doing a
synchronous update is the simplest way to handle this. Was it
necessary to change this given the other changes you are making the fs
freeze implementation?
- Ted
Powered by blists - more mailing lists