From: Andrew Morton <akpm@linux-foundation.org>
To: Mingming Cao <cmm@us.ibm.com>
Cc: jack@suse.cz, tytso@mit.edu, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH V2 1/3] quota: Add reservation support for delayed block allocation
Date: Tue, 4 Nov 2008 17:14:51 -0800 [thread overview]
Message-ID: <20081104171451.816d92d0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1225488442.7600.12.camel@mingming-laptop>
On Fri, 31 Oct 2008 14:27:22 -0700
Mingming Cao <cmm@us.ibm.com> wrote:
> +int dquot_alloc_space(struct inode *inode, qsize_t number, int warn)
> +{
> + int cnt, ret = QUOTA_OK;
> +
> + /*
> + * First test before acquiring mutex - solves deadlocks when we
> + * re-enter the quota code and are already holding the mutex
> + */
> + if (IS_NOQUOTA(inode)) {
> + inode_add_bytes(inode, number);
> + return ret;
> + }
> +
> + down_read(&sb_dqopt(inode->i_sb)->dqptr_sem);
> + if (IS_NOQUOTA(inode)) {
> + /* Now we can do reliable test... */
> + up_read(&sb_dqopt(inode->i_sb)->dqptr_sem);
> + inode_add_bytes(inode, number);
> + return ret;
> + }
> +
> + ret = __dquot_alloc_space(inode, number, warn, 0);
> + if (ret == NO_QUOTA) {
> + up_read(&sb_dqopt(inode->i_sb)->dqptr_sem);
> + return ret;
> + }
> +
> + /* Dirtify all the dquots - this can block when journalling */
> + for (cnt = 0; cnt < MAXQUOTAS; cnt++)
> + if (inode->i_dquot[cnt])
> + mark_dquot_dirty(inode->i_dquot[cnt]);
> + up_read(&sb_dqopt(inode->i_sb)->dqptr_sem);
> + inode_add_bytes(inode, number);
> + return ret;
> +}
I'm going to have to call "ug" on that code.
Multiple return points per function really is a maintenance problem.
It's a great source of code duplication, locking errors and resource
leaks as the code evolves.
Can we please rework this code (and any other similar code here) to use
the usual `goto out' pattern?
int dquot_alloc_space(struct inode *inode, qsize_t number, int warn)
{
int cnt, ret = QUOTA_OK;
/*
* First test before acquiring mutex - solves deadlocks when we
* re-enter the quota code and are already holding the mutex
*/
if (IS_NOQUOTA(inode))
goto out;
down_read(&sb_dqopt(inode->i_sb)->dqptr_sem);
if (IS_NOQUOTA(inode)) /* Now we can do reliable test... */
goto out_unlock;
ret = __dquot_alloc_space(inode, number, warn, 0);
if (ret == NO_QUOTA) {
up_read(&sb_dqopt(inode->i_sb)->dqptr_sem);
return ret;
}
<<
I don't know what to do here - did we really want to skip the
inode_add_bytes? If so, we could do
number = 0;
goto out_unlock;
>>
/* Dirtify all the dquots - this can block when journalling */
for (cnt = 0; cnt < MAXQUOTAS; cnt++)
if (inode->i_dquot[cnt])
mark_dquot_dirty(inode->i_dquot[cnt]);
out_unlock:
up_read(&sb_dqopt(inode->i_sb)->dqptr_sem);
out:
inode_add_bytes(inode, number);
return ret;
}
or something like that.
next prev parent reply other threads:[~2008-11-05 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 21:27 [PATCH V2 1/3] quota: Add reservation support for delayed block allocation Mingming Cao
2008-11-05 1:14 ` Andrew Morton [this message]
2008-11-06 23:28 ` Mingming Cao
2008-11-06 23:36 ` [PATCH V3 2/3] quota: Add quota claim and release reserved quota blocks operations Mingming Cao
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=20081104171451.816d92d0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cmm@us.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).