linux-ext4 - [PATCH] jbd2: We shouldnot cap writeback when we are doing a journal commit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1214590065-26891-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
Date:	Fri, 27 Jun 2008 23:37:45 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	cmm@...ibm.com, tytso@....edu, sandeen@...hat.com, jack@...e.cz
Cc:	linux-ext4@...r.kernel.org,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: [PATCH] jbd2: We shouldnot cap writeback when we are doing a journal commit

A journal commit need to make sure we submit data buffers before
we submit the meta-data buffers in ordered mode. We should
not be looking at BDI_CAP_NO_WRITEBACK when doing a journal commit.

Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@...ux.vnet.ibm.com>
---
 fs/jbd2/commit.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/fs/jbd2/commit.c b/fs/jbd2/commit.c
index 32ca3c3..f8b3be8 100644
--- a/fs/jbd2/commit.c
+++ b/fs/jbd2/commit.c
@@ -203,9 +203,6 @@ static int journal_submit_inode_data_buffers(struct address_space *mapping)
 		.for_writepages = 1,
 	};
 
-	if (!mapping_cap_writeback_dirty(mapping))
-		return 0;
-
 	ret = generic_writepages(mapping, &wbc);
 	return ret;
 }
-- 
1.5.6.1.78.gde8d9.dirty

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html