From: Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, Dmitry Monakhov <dmonakhov@openvz.org>
Subject: [PATCH 3/7] vfs: do not allow inode_setattr() to fail after vfs_dq_transfer()
Date: Fri, 19 Feb 2010 22:47:21 +0300 [thread overview]
Message-ID: <1266608845-13212-4-git-send-email-dmonakhov@openvz.org> (raw)
In-Reply-To: <1266608845-13212-3-git-send-email-dmonakhov@openvz.org>
After quota was transfered, inode_setattr() may fail. This
is tricky situation because it may be impossible to
roll-back quota changes. But we have already done all
necessery changes in inode_change_ok() so it is safe to
use nofail version of inode_seattr() here.
Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
---
fs/attr.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/fs/attr.c b/fs/attr.c
index cc2a801..c1ae61c 100644
--- a/fs/attr.c
+++ b/fs/attr.c
@@ -243,7 +243,11 @@ int notify_change(struct dentry * dentry, struct iattr * attr)
error = vfs_dq_transfer(inode, attr) ?
-EDQUOT : 0;
if (!error)
- error = inode_setattr(inode, attr);
+ /*
+ * All necessery check already done, it is
+ * safe to use nofail version here.
+ */
+ __inode_setattr(inode, attr);
}
}
--
1.6.6
next prev parent reply other threads:[~2010-02-19 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 19:47 [PATCH 0/7] vfs: notify_changes() error handling Dmitry Monakhov
2010-02-19 19:47 ` [PATCH 1/7] mm: add nofail version of vmtruncate() and inode_setattr() Dmitry Monakhov
2010-02-19 19:47 ` [PATCH 2/7] vfs: inode_change_ok have to perform all necessery checks Dmitry Monakhov
2010-02-19 19:47 ` Dmitry Monakhov [this message]
2010-02-19 19:47 ` [PATCH 4/7] ext2: use nofail variant of inode_setattr() Dmitry Monakhov
2010-02-19 19:47 ` [PATCH 5/7] ext3: " Dmitry Monakhov
2010-02-19 19:47 ` [PATCH 6/7] ext4: " Dmitry Monakhov
2010-02-19 19:47 ` [PATCH 7/7] ocfs2: " Dmitry Monakhov
2010-02-22 10:35 ` [PATCH 0/7] vfs: notify_changes() error handling Jan Kara
2010-02-22 11:15 ` Nick Piggin
2010-02-22 13:30 ` Dmitry Monakhov
2010-02-22 14:56 ` Nick Piggin
2010-02-22 17:37 ` Dmitry Monakhov
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=1266608845-13212-4-git-send-email-dmonakhov@openvz.org \
--to=dmonakhov@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).