From: Zach Brown <zach.brown@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: btrfs-devel@oss.oracle.com, linux-btrfs@vger.kernel.org
Subject: Re: [Btrfs-devel] transaction ioctls
Date: Tue, 22 Apr 2008 13:29:25 -0700 [thread overview]
Message-ID: <480E4AA5.1070700@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804221210130.23551@cobra.newdream.net>
> A misbehaving application could also deliberately hold a transaction open,
> effectively locking up the FS, so it may make sense to restrict something
> like this to root or something.
I suspect it doesn't have to be deliberate.
Have you tried this under memory pressure? I wonder if the application
can get stuck waiting for memory which will only be freed once the
transaction closes.
I'm reasonably sure that we've discussed this persistent theoretical
problem with these kinds of interfaces ;).
- z
next parent reply other threads:[~2008-04-22 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0804221210130.23551@cobra.newdream.net>
2008-04-22 20:29 ` Zach Brown [this message]
2008-04-22 20:41 ` [Btrfs-devel] transaction ioctls Chris Mason
2008-04-22 20:52 ` Sage Weil
2008-04-22 20:55 ` Chris Mason
2008-04-22 20:56 ` Sage Weil
2008-04-22 21:05 ` Evgeniy Polyakov
2008-04-23 12:50 ` Chris Mason
2008-04-23 12:57 ` Evgeniy Polyakov
2008-04-23 13:07 ` Chris Mason
2008-04-23 13:15 ` Evgeniy Polyakov
2008-04-23 13:23 ` Chris Mason
[not found] ` <200804230923.03752.chris.mason@oracle.com>
2008-04-23 16:21 ` Evgeniy Polyakov
2008-04-23 17:15 ` Chris Mason
2008-04-23 23:52 ` Bron Gondwana
2008-04-24 13:06 ` Chris Mason
[not found] ` <200804240906.54788.chris.mason@oracle.com>
2008-04-27 10:55 ` Bron Gondwana
2008-04-23 17:12 ` btrfs-devel
2008-04-22 20:32 ` Chris Mason
2008-04-22 20:48 ` Sage Weil
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=480E4AA5.1070700@oracle.com \
--to=zach.brown@oracle.com \
--cc=btrfs-devel@oss.oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@newdream.net \
/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.