linux-kernel - kobject.c changes in -mm

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]

Date:	Mon, 8 Jan 2007 13:37:47 +0000
From:	Christoph Hellwig <hch@...radead.org>
To:	akpm@...l.org, gregkh@...e.de
Cc:	linux-kernel@...r.kernel.org
Subject: kobject.c changes in -mm

--- linux-2.6.20-rc3/lib/kobject.c      2007-01-01 23:04:49.000000000 -0800
+++ devel/lib/kobject.c 2007-01-04 21:13:21.000000000 -0800
@@ -15,6 +15,8 @@
 #include <linux/module.h>
 #include <linux/stat.h>
 #include <linux/slab.h>
+#include <linux/kallsyms.h>
+#include <asm-generic/sections.h>

+#ifdef CONFIG_X86_32
+static int ptr_in_range(void *ptr, void *start, void *end)
+{
+       /*
+        * This should hopefully get rid of causing warnings
+        * if the architecture did not set one of the section
+        * variables up.
+        */ 
+       if (start >= end)
+               return 0;
+
+       if ((ptr >= start) && (ptr < end))
+               return 1;
+       return 0;
+}      

Can anyone explain WTF is going on here?  Including asm-generic headers
in core code definitly is not okay.  As are random CONFIG_X86_32 ifdefs
in said code.
-
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/