linux-kernel - data structure for NT_386_LTS note entry in coredump

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: <CAD-N9QVDwM1MkhqW_W3OFjcSttFd+Xe6R57dSj09HoZSnCyO1g@mail.gmail.com>
Date:   Wed, 5 Oct 2016 12:13:37 -0400
From:   慕冬亮 <mudongliangabcd@...il.com>
To:     kernelnewbies <kernelnewbies@...nelnewbies.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: data structure for NT_386_LTS note entry in coredump

Dear all,

I have a question about data structure for NT_386_LTS note entry in
coredump and where is the code to store this entry into coredump.

When I analyzed coredump and corresponding assembly code, I found
there is one memory addressing with gs. GS is a selector used by
glibc. But its base address is stored in the kernel space which I
don't know from "gdb executable core". But fortunately I find a note
entry with type NT_386_LTS in my coredump.

The following is the content of this note entry,
>> LINUX                 48  386_TLS
>>     index: 6, base: 0xb7fd57c0, limit: 0x000fffff, flags: 0x00000051
>>     index: 7, base: 0x00000000, limit: 0x00000000, flags: 0x00000028
>>     index: 8, base: 0x00000000, limit: 0x00000000, flags: 0x00000028

Q1: Is there a data structure defined in header file like /usr/include/elf.h?
Q2: Where is the code to store this entry into coredump?

--
My best regards to you.

     No System Is Safe!
     Dongliang Mu