From: akpm@linux-foundation.org
To: joseph.qi@huawei.com, alex.chen@huawei.com, jlbec@evilplan.org,
mfasheh@suse.com, wangww631@huawei.com, xuejiufei@huawei.com,
mm-commits@vger.kernel.org
Subject: [folded-merged] ocfs2-implement-ocfs2_direct_io_write-fix.patch removed from -mm tree
Date: Mon, 15 Dec 2014 14:28:54 -0800 [thread overview]
Message-ID: <548f60a6.CI5J53lsgde4sVaW%akpm@linux-foundation.org> (raw)
The patch titled
Subject: ocfs2: fix brelse warning if ocfs2_direct_IO_get_blocks failed
has been removed from the -mm tree. Its filename was
ocfs2-implement-ocfs2_direct_io_write-fix.patch
This patch was dropped because it was folded into ocfs2-implement-ocfs2_direct_io_write.patch
------------------------------------------------------
From: Joseph Qi <joseph.qi@huawei.com>
Subject: ocfs2: fix brelse warning if ocfs2_direct_IO_get_blocks failed
In ocfs2_direct_IO_write, if ocfs2_direct_IO_get_blocks failed, the
di_bh will be used again in unlikely branch, and this will hit a warning
"VFS: brelse: Trying to free free buffer" when jbd2 do checkpoint.
Fix this issue by setting di_bh to NULL after brelse.
Reported-by: alex chen <alex.chen@huawei.com>
Signed-off-by: Joseph Qi <joseph.qi@huawei.com>
Reviewed-by: joyce.xue <xuejiufei@huawei.com>
Cc: Weiwei Wang <wangww631@huawei.com>
Cc: Joel Becker <jlbec@evilplan.org>
Cc: Mark Fasheh <mfasheh@suse.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/ocfs2/aops.c | 1 +
1 file changed, 1 insertion(+)
diff -puN fs/ocfs2/aops.c~ocfs2-implement-ocfs2_direct_io_write-fix fs/ocfs2/aops.c
--- a/fs/ocfs2/aops.c~ocfs2-implement-ocfs2_direct_io_write-fix
+++ a/fs/ocfs2/aops.c
@@ -692,6 +692,7 @@ static ssize_t ocfs2_direct_IO_write(str
ocfs2_inode_unlock(inode, 1);
brelse(di_bh);
+ di_bh = NULL;
}
written = __blockdev_direct_IO(WRITE, iocb, inode, inode->i_sb->s_bdev,
_
Patches currently in -mm which might be from joseph.qi@huawei.com are
origin.patch
ocfs2-dlm-fix-race-between-dispatched_work-and-dlm_lockres_grab_inflight_worker.patch
ocfs2-eliminate-the-static-flag-of-some-functions.patch
ocfs2-add-functions-to-add-and-remove-inode-in-orphan-dir.patch
ocfs2-add-orphan-recovery-types-in-ocfs2_recover_orphans.patch
ocfs2-implement-ocfs2_direct_io_write.patch
ocfs2-allocate-blocks-in-ocfs2_direct_io_get_blocks.patch
ocfs2-do-not-fallback-to-buffer-i-o-write-if-appending.patch
ocfs2-do-not-fallback-to-buffer-i-o-write-if-fill-holes.patch
ocfs2-fix-leftover-orphan-entry-caused-by-append-o_direct-write-crash.patch
next reply other threads:[~2014-12-15 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 22:28 akpm [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-16 23:48 [folded-merged] ocfs2-implement-ocfs2_direct_io_write-fix.patch removed from -mm tree akpm
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=548f60a6.CI5J53lsgde4sVaW%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alex.chen@huawei.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=wangww631@huawei.com \
--cc=xuejiufei@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox