linux-kernel - ./scripts/kallsysm.c question

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: <200705221420.26693.rgetz@blackfin.uclinux.org>
Date:	Tue, 22 May 2007 14:20:26 -0400
From:	Robin Getz <rgetz@...ckfin.uclinux.org>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	"LKML" <linux-kernel@...r.kernel.org>
Subject: ./scripts/kallsysm.c question

Sam:

I was noticing some issues with /proc/kallsyms generation on our platform, 
which I noticed after a toolchain update (which I fixed)

However, I had a question in looking at the logic - it looks like the out 
function puts out all symbols - even if they are in the _init section. My
question was should it?

I can see some issues if someone built a module against a function that was
marked as init - when the module loaded - the init code is gone, but the 
symbol is still in the kernel - isn't it? a module would jump to where the
code use to be - which might be something else at the time.

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