From: Mark Fasheh <mfasheh@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Fix estimate of necessary credits for mkdir
Date: Thu, 3 Feb 2011 10:13:15 -0800 [thread overview]
Message-ID: <20110203181315.GC1703@wotan.suse.de> (raw)
In-Reply-To: <1296738979-27791-1-git-send-email-jack@suse.cz>
On Thu, Feb 03, 2011 at 02:16:19PM +0100, Jan Kara wrote:
> In the rare case that INLINE_DATA, INDEX_DIR, QUOTA, XATTR features are
> disabled and both the allocation of the directory inode and the allocation
> of the first directory block need to relink allocation group, there need
> not be enough credits reserved in a transaction. Fix the estimate.
>
> CC: Mark Fasheh <mfasheh@suse.de>
> Signed-off-by: Jan Kara <jack@suse.cz>
Acked-by: Mark Fasheh <mfasheh@suse.com>
--
Mark Fasheh
next prev parent reply other threads:[~2011-02-03 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 13:16 [Ocfs2-devel] [PATCH] ocfs2: Fix estimate of necessary credits for mkdir Jan Kara
2011-02-03 18:13 ` Mark Fasheh [this message]
2011-02-20 10:41 ` Joel Becker
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=20110203181315.GC1703@wotan.suse.de \
--to=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).