[ext2resize] Re: Deadlock help

[Robert W. <rj...@du...>]

> The intention is that other processes cannot start using the new space
> until it is completely set up.  We want to avoid a situation where a
> file is allocated in the new space, and then we say "oops, there was a
> problem, let's yank that new space back" =3D=3D missing data.
>=20
> I think this can be done fairly cleanly by ensuring everything is set up
> before updating the superblock (in memory and on disk), and only holding
> the lock over that update.  For extend-the-end resizing, we already have
> to drop the lock for ext3_free_blocks(), because it gets the lock itself.

Until we get around to doing this, do you think the existing solution of
dropping the lock before calling journal_start or journal_stop and
reacquiring it after is sufficient?

Regards,
 Robert.

--=20
Robert Walsh
Amalgamated Durables, Inc.  -  "We don't make the things you buy."
Email: rj...@du...