linux-kernel - [PATCH] Fix a missing inclusion of linux/types.h in linux/fs.h

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: <20101028072528.31276.91746.stgit@warthog.procyon.org.uk>
Date:	Thu, 28 Oct 2010 08:25:28 +0100
From:	David Howells <dhowells@...hat.com>
To:	torvalds@...l.org, akpm@...ux-foundation.org
Cc:	lczerner@...hat.com, dmonakhov@...nvz.org, tytso@....edu,
	linux-kernel@...r.kernel.org
Subject: [PATCH] Fix a missing inclusion of linux/types.h in linux/fs.h

linux/fs.h needs to #include linux/types.h otherwise the following errors can be
encountered:

In file included from fs/char_dev.c:8:
include/linux/fs.h:36: error: expected specifier-qualifier-list before 'uint64_t'
In file included from include/linux/tty.h:9,
                 from drivers/char/tty_mutex.c:4:
include/linux/fs.h:36: error: expected specifier-qualifier-list before 'uint64_t'
In file included from mm/shmem.c:23:
include/linux/fs.h:36: error: expected specifier-qualifier-list before 'uint64_t'

Signed-off-by: David Howells <dhowells@...hat.com>
---

 include/linux/fs.h |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)


diff --git a/include/linux/fs.h b/include/linux/fs.h
index 6ed7ace..15de46d 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -6,6 +6,7 @@
  * structures etc.
  */
 
+#include <linux/types.h>
 #include <linux/limits.h>
 #include <linux/ioctl.h>
 #include <linux/blk_types.h>

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