From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: htl10@users.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] hfsplus: rework processing of hfs_btree_write() returned error
Date: Mon, 03 Dec 2012 10:02:42 +0400 [thread overview]
Message-ID: <1354514562.2547.2.camel@slavad-ubuntu> (raw)
In-Reply-To: <1354364883.63654.YahooMailClassic@web172306.mail.ir2.yahoo.com>
On Sat, 2012-12-01 at 12:28 +0000, Hin-Tak Leung wrote:
[snip]
> if (err) {
> > +
> > printk(KERN_ERR "hfs: unable to write b-tree\n");
> > +
> > dprint(DBG_INODE, "hfsplus_system_write_inode: %lu\n",
> > +
> > inode->i_ino);
> > +
> > return err;
> > + }
> > + }
> > return 0;
> > }
> >
>
> There is a small issue which crossed my mind when I first noticed with:
> "hfsplus: rework processing errors in hfsplus_free_extents()"
>
> It is a printk() followed by dprint() with additional information, on error. Because dprint() needs a compile-time change (or at least, echo'ing into debugfs if switched to dynamic-debug). This means the additional information would not be seen the first time the error occurred. I am wondering whether the additional info should be included in the printk - in a short-hand form, maybe?
>
I think that your remark is reasonable. I'll prepare the patch.
Thanks,
Vyacheslav Dubeyko.
> Hin-Tak
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-12-03 6:02 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
2012-12-01 13:16 ` Vyacheslav Dubeyko
2012-12-01 12:28 ` Hin-Tak Leung
2012-12-03 6:02 ` Vyacheslav Dubeyko [this message]
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=1354514562.2547.2.camel@slavad-ubuntu \
--to=slava@dubeyko.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=htl10@users.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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).