linux-kernel - [PATCH 2 of 2]: Make XFS use BH_Unwritten and BH

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>] [day] [month] [year] [list]

Message-ID: <20070110003819.GO44411608@melbourne.sgi.com>
Date:	Wed, 10 Jan 2007 11:38:19 +1100
From:	David Chinner <dgc@....com>
To:	linux-fsdevel@...r.kernel.org
Cc:	hch@...radead.org, linux-kernel@...r.kernel.org, xfs@....sgi.com
Subject: [PATCH 2 of 2]: Make XFS use BH_Unwritten and BH_Delay correctly


Don't hide buffer_unwritten behind buffer_delay() and
remove the hack that clears unexpected buffer_unwritten()
states now that it can't happen.

Signed-Off-By: Dave Chinner <dgc@....com>

---
 fs/xfs/linux-2.6/xfs_aops.c |   3 ---
 1 file changed, 29 deletions(-)

Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_aops.c
===================================================================
--- 2.6.x-xfs-new.orig/fs/xfs/linux-2.6/xfs_aops.c	2007-01-08 12:21:40.000000000 +1100
+++ 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_aops.c	2007-01-09 11:05:09.763127643 +1100
@@ -58,8 +58,6 @@ xfs_count_page_state(
 	do {
 		if (buffer_uptodate(bh) && !buffer_mapped(bh))
 			(*unmapped) = 1;
-		else if (buffer_unwritten(bh) && !buffer_delay(bh))
-			clear_buffer_unwritten(bh);
 		else if (buffer_unwritten(bh))
 			(*unwritten) = 1;
 		else if (buffer_delay(bh))
@@ -1271,7 +1269,6 @@ __xfs_get_blocks(
 			if (direct)
 				bh_result->b_private = inode;
 			set_buffer_unwritten(bh_result);
-			set_buffer_delay(bh_result);
 		}
 	}
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/