linux-kernel - debug data for per-cpu variable offsets

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CABg=H3MScbDmuZgr_Ax3MgEgNjcqN+1vWQ=TjaUisY38XaKnuA@mail.gmail.com>
Date:	Fri, 2 Aug 2013 12:07:30 -0700
From:	Deep Debroy <ddebroy@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: debug data for per-cpu variable offsets

Hi, for x86_64 platforms, I was wondering if there is any table of
per-cpu variable offsets left in a (unstripped) vmlinux file. Looking
at the disassembly of routines accessing a per-cpu variables like
current_task, we see the offset hardcoded e.g. mov %gs:0xc500,%rax. Is
there any table in some section in unstripped vmlinux that indicates
current_task is at offset 0xc500 from gs base (similar to how a
struct's members and offsets are enumerated in the debug sections of
vmlinux)?

thanks,
Deep
--
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/