From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
Andrew Morton <andrewm@uow.edu.au>
Subject: Re: Linux-2.4.10 + ext3
Date: Thu, 27 Sep 2001 19:37:50 +0100 [thread overview]
Message-ID: <20010927193750.I16055@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109231142060.1078-100000@penguin.transmeta.com> <1001280620.3540.33.camel@gromit.house> <9om4ed$1hv$1@penguin.transmeta.com> <20010926174943.W3437@redhat.com> <20010927141244.F26535@atrey.karlin.mff.cuni.cz>
In-Reply-To: <20010927141244.F26535@atrey.karlin.mff.cuni.cz>; from jack@suse.cz on Thu, Sep 27, 2001 at 02:12:44PM +0200
Hi,
On Thu, Sep 27, 2001 at 02:12:44PM +0200, Jan Kara wrote:
> > And there are recursions we just can't get rid of --- an inode delete
> > ends up deallocating the inode on disk and updating the dquot (which
> > does a dqput, which writes the quota entry using the normal VFS API),
> > and we _have_ to make that quota-file write a nested transaction if we
> > want quotas to be atomic with respect to journal recovery. Short of
> > adding a new context parameter to be passed all the way through the
> > quota and VM layers wherever this sort of recursion is possible, we
> > need to attach that context to the task. (Without a task struct
> > field, though, we can still hash outstanding transaction handles by
> > pid for fast lookup.)
> Actually Alan should now have patch in his queue which makes
> quota guarantee no recursion on DQUOT_ALLOC/FREE operations (apart from
> mark_inode_dirty()). Recursion is possible only in DQUOT_DROP,
> DQUOT_INIT and DQUOT_TRANSFER. So this patch might help ext3 a bit.
Possibly: it might be possible to defer the dquot_drop until after
we've closed the transaction which deleted the inode. Thanks.
Cheers,
Stephen
next prev parent reply other threads:[~2001-09-27 18:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-23 18:54 Linux-2.4.10 Linus Torvalds
2001-09-23 16:41 ` Linux-2.4.10 Rob Landley
2001-09-23 21:32 ` Linux-2.4.10 André Dahlqvist
2001-09-23 21:54 ` Linux-2.4.10 Alan Cox
2001-09-23 21:30 ` Linux-2.4.10 + ext3 Michael Rothwell
2001-09-23 22:18 ` Gergely Nagy
2001-09-24 2:06 ` Linus Torvalds
2001-09-24 2:30 ` Aaron Lehmann
2001-09-24 3:45 ` Andrew Morton
2001-09-24 4:35 ` Simon Fowler
2001-09-24 20:40 ` Stephen C. Tweedie
2001-09-24 4:45 ` Aaron Lehmann
2001-09-24 5:19 ` Andrew Morton
2001-09-24 19:49 ` Jamie Lokier
2001-09-24 20:22 ` Chris Meadors
2001-09-24 21:57 ` Jamie Lokier
2001-09-24 21:04 ` Andreas Dilger
2001-09-24 18:12 ` Linus Torvalds
2001-09-24 18:25 ` Alexander Viro
2001-09-26 16:49 ` Stephen C. Tweedie
2001-09-27 12:12 ` Jan Kara
2001-09-27 18:37 ` Stephen C. Tweedie [this message]
2001-09-23 21:54 ` Linux-2.4.10 Trond Myklebust
2001-09-23 22:34 ` Linux-2.4.10 David Woodhouse
2001-09-24 6:28 ` Linux-2.4.10 Erik Andersen
2001-09-24 6:48 ` Linux-2.4.10 David Woodhouse
2001-09-24 17:40 ` Linux-2.4.10 Erik Andersen
2001-09-24 17:41 ` Linux-2.4.10 David Woodhouse
2001-09-23 22:40 ` Linux-2.4.10 - necessary patches Eyal Lebedinsky
2001-09-24 0:04 ` Alan Cox
2001-09-24 14:42 ` Oliver Xymoron
2001-09-24 1:25 ` Linux-2.4.10 Matthias Andree
2001-09-24 2:26 ` Linux-2.4.10 Daniel T. Chen
2001-09-24 3:19 ` Linux-2.4.10 Matthias Andree
2001-09-24 2:57 ` Linux-2.4.10 Disconnect
2001-09-24 10:07 ` Linux-2.4.10 Matthias Andree
2001-09-27 12:17 ` Linux-2.4.10 Roeland Th. Jansen
2001-09-24 2:35 ` Linux-2.4.10 Naren Devaiah
2001-09-24 9:37 ` PATCH[2.4.9-pre14] Kill *writeonly* variable Martin Dalecki
2001-09-27 15:23 ` Linux-2.4.10 George R. Kasica
2001-09-27 15:27 ` Linux-2.4.10 Rik van Riel
2001-09-27 15:31 ` Linux-2.4.10 Bernd Petrovitsch
2001-09-27 15:49 ` Linux-2.4.10 John Jasen
2001-09-27 18:23 ` Linux-2.4.10 Petr Baudis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010927193750.I16055@redhat.com \
--to=sct@redhat.com \
--cc=andrewm@uow.edu.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.