linux-kernel - [PATCH] vfs, doc: Remove reference to nonexistent FIEMAP_EXTENT_NO

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: <1340548325-27648-1-git-send-email-hpa@zytor.com>
Date:	Sun, 24 Jun 2012 07:32:05 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Al Viro <viro@...iv.linux.org.uk>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Cc:	"H. Peter Anvin" <hpa@...or.com>
Subject: [PATCH] vfs, doc: Remove reference to nonexistent FIEMAP_EXTENT_NO_BYPASS

From: "H. Peter Anvin" <hpa@...or.com>

Presumably this was a flag that was intended to have been created at
some point, but never was.  There are no other references to it
anywhere in the source tree.

Signed-off-by: H. Peter Anvin <hpa@...or.com>
---
 include/linux/fiemap.h |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/include/linux/fiemap.h b/include/linux/fiemap.h
index d830747..645ef70 100644
--- a/include/linux/fiemap.h
+++ b/include/linux/fiemap.h
@@ -49,8 +49,7 @@ struct fiemap {
 						    * Sets EXTENT_UNKNOWN. */
 #define FIEMAP_EXTENT_ENCODED		0x00000008 /* Data can not be read
 						    * while fs is unmounted */
-#define FIEMAP_EXTENT_DATA_ENCRYPTED	0x00000080 /* Data is encrypted by fs.
-						    * Sets EXTENT_NO_BYPASS. */
+#define FIEMAP_EXTENT_DATA_ENCRYPTED	0x00000080 /* Data is encrypted by fs.*/
 #define FIEMAP_EXTENT_NOT_ALIGNED	0x00000100 /* Extent offsets may not be
 						    * block aligned. */
 #define FIEMAP_EXTENT_DATA_INLINE	0x00000200 /* Data mixed with metadata.
-- 
1.7.10.2

--
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/