From: Andrew Morton <akpm@linux-foundation.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Hin-Tak Leung <htl10@users.sourceforge.net>
Subject: Re: [PATCH] hfsplus: rework processing of hfs_btree_write() returned error
Date: Fri, 30 Nov 2012 13:56:19 -0800 [thread overview]
Message-ID: <20121130135619.101accf9.akpm@linux-foundation.org> (raw)
In-Reply-To: <1354272566.2069.6.camel@slavad-ubuntu>
On Fri, 30 Nov 2012 14:49:26 +0400
Vyacheslav Dubeyko <slava@dubeyko.com> wrote:
> Hi,
>
> The patch adds in hfs_btree_write() returning of -EIO in the case of failing of b-tree's node searching.
>
> With the best regards,
> Vyacheslav Dubeyko.
> --
> From: Vyacheslav Dubeyko <slava@dubeyko.com>
> Subject: [PATCH] hfsplus: rework processing of hfs_btree_write() returned error
>
> The patch adds in hfs_btree_write() returning of -EIO in the case of failing of b-tree's node searching. It is added also logic of processing errors of hfs_btree_write() in hfsplus_system_write_inode() with message about b-tree writing failure.
>
> Signed-off-by: Vyacheslav Dubeyko <slava@dubeyko.com>
We don't need two changelogs for each patch ;) The patch's formal
changelog text should be sufficient.
> fs/hfsplus/btree.c | 5 +++--
> fs/hfsplus/hfsplus_fs.h | 2 +-
> fs/hfsplus/super.c | 12 ++++++++++--
> 3 files changed, 14 insertions(+), 5 deletions(-)
I modified a couple of things, please review:
From: Andrew Morton <akpm@linux-foundation.org>
Subject: hfsplus-rework-processing-of-hfs_btree_write-returned-error-fix
reduce scope of `err', print errno on error
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: Vyacheslav Dubeyko <slava@dubeyko.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/hfsplus/super.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/fs/hfsplus/super.c~hfsplus-rework-processing-of-hfs_btree_write-returned-error-fix
+++ a/fs/hfsplus/super.c
@@ -100,7 +100,6 @@ static int hfsplus_system_write_inode(st
struct hfsplus_vh *vhdr = sbi->s_vhdr;
struct hfsplus_fork_raw *fork;
struct hfs_btree *tree = NULL;
- int err;
switch (inode->i_ino) {
case HFSPLUS_EXT_CNID:
@@ -131,9 +130,10 @@ static int hfsplus_system_write_inode(st
}
hfsplus_inode_write_fork(inode, fork);
if (tree) {
- err = hfs_btree_write(tree);
+ int err = hfs_btree_write(tree);
if (err) {
- printk(KERN_ERR "hfs: unable to write b-tree\n");
+ printk(KERN_ERR "hfs: unable to write b-tree: %d\n",
+ err);
dprint(DBG_INODE, "hfsplus_system_write_inode: %lu\n",
inode->i_ino);
return err;
_
next prev parent reply other threads:[~2012-11-30 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 10:49 [PATCH] hfsplus: rework processing of hfs_btree_write() returned error Vyacheslav Dubeyko
2012-11-30 21:56 ` Andrew Morton [this message]
2012-12-01 13:16 ` Vyacheslav Dubeyko
2012-12-01 12:28 ` Hin-Tak Leung
2012-12-03 6:02 ` Vyacheslav Dubeyko
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=20121130135619.101accf9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=htl10@users.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=viro@zeniv.linux.org.uk \
/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).