From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: do not put bh when buffer_uptodate failed
Date: Wed, 26 Mar 2014 19:22:08 -0700 [thread overview]
Message-ID: <20140327022207.GA5215@localhost> (raw)
In-Reply-To: <53312AD6.4080607@huawei.com>
On Tue, Mar 25, 2014 at 03:05:58PM +0800, alex chen wrote:
> Do not put bh when buffer_uptodate failed in ocfs2_write_block and
> ocfs2_write_super_or_backup, because it will put bh in b_end_io.
> Otherwise it will hit a warning "VFS: brelse: Trying to free free
> buffer".
>
> Signed-off-by: Alex Chen <alex.chen@huawei.com>
> Reviewed-by: Joseph Qi <joseph.qi@huawei.com>
Good catch. Can you tell me what testing or workload found this issue?
Just for future reference.
Acked-by: Joel Becker <jlbec@evilplan.org>
> ---
> fs/ocfs2/buffer_head_io.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/ocfs2/buffer_head_io.c b/fs/ocfs2/buffer_head_io.c
> index 5b704c6..1edcb14 100644
> --- a/fs/ocfs2/buffer_head_io.c
> +++ b/fs/ocfs2/buffer_head_io.c
> @@ -90,7 +90,6 @@ int ocfs2_write_block(struct ocfs2_super *osb, struct buffer_head *bh,
> * information for this bh as it's not marked locally
> * uptodate. */
> ret = -EIO;
> - put_bh(bh);
> mlog_errno(ret);
> }
>
> @@ -420,7 +419,6 @@ int ocfs2_write_super_or_backup(struct ocfs2_super *osb,
>
> if (!buffer_uptodate(bh)) {
> ret = -EIO;
> - put_bh(bh);
> mlog_errno(ret);
> }
>
> --
> 1.8.4.3
>
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
--
Life's Little Instruction Book #497
"Go down swinging."
http://www.jlbec.org/
jlbec at evilplan.org
next prev parent reply other threads:[~2014-03-27 2:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 7:05 [Ocfs2-devel] [PATCH] ocfs2: do not put bh when buffer_uptodate failed alex chen
2014-03-25 18:45 ` Srinivas Eeda
2014-03-26 1:25 ` alex chen
2014-03-26 17:10 ` Srinivas Eeda
2014-03-27 2:22 ` Joel Becker [this message]
2014-03-28 1:33 ` alex chen
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=20140327022207.GA5215@localhost \
--to=jlbec@evilplan.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.