search for: st_info

...Error inserting zaphfc (/lib/modules/2.6.11.4-20a-default/misc/zaphfc.ko): Unknown symbol in module, or unknown parameter (see dmesg) My dmesg output: zaphfc: unsupported module, tainting kernel. zaphfc: disagrees about version of symbol zt_receive zaphfc: Unknown symbol zt_receive, st_info == 0x1 zaphfc: disagrees about version of symbol zt_ec_chunk zaphfc: Unknown symbol zt_ec_chunk, st_info == 0x1 zaphfc: disagrees about version of symbol zt_transmit zaphfc: Unknown symbol zt_transmit, st_info == 0x1 zaphfc: disagrees about version of symbol zt_unregister zaphfc: Unknown symb...

...i-t build against klibc, so i propose to kill the old local insmod copy. sent the only local m-i-t fix upstream, please pull: git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks maximilian attems (3): [klibc] klibc/socketcalls/.gitignore addition [klibc] elf.h add support for st_info field [klibc] remove local insmod.c copy and diffstat usr/include/sys/elf32.h | 4 usr/include/sys/elf64.h | 4 usr/include/sys/elfcommon.h | 10 ++ usr/klibc/socketcalls/.gitignore | 1 usr/utils/Kbuild | 4 usr/utils/insmod.c...

...zaptel gl0:/usr/src/zaptel-1.0.8 # the end bit of dmesg returns: zaptel: unsupported module, tainting kernel. Zapata Telephony Interface Registered on major 196 ztdummy: unsupported module, tainting kernel. ztdummy: disagrees about version of symbol zt_receive ztdummy: Unknown symbol zt_receive, st_info == 0x1 ztdummy: disagrees about version of symbol zt_transmit ztdummy: Unknown symbol zt_transmit, st_info == 0x1 ztdummy: disagrees about version of symbol zt_unregister ztdummy: Unknown symbol zt_unregister, st_info == 0x1 ztdummy: disagrees about version of symbol zt_register ztdummy: Unknown sy...

...libc-0.178/include/sys/elf32.h 2004-01-30 14:40:51.000000000 -0700 +++ klibc-0.178-fogo/include/sys/elf32.h 2004-09-20 09:15:58.000000000 -0600 @@ -7,6 +7,10 @@ #include <sys/elfcommon.h> +#define ELF32_ST_BIND(val) ST_BIND (val) +#define ELF32_ST_TYPE(val) ST_TYPE (val) +#define ELF32_ST_INFO(bind, type) ST_INFO ((bind), (type)) + /* ELF standard typedefs (yet more proof that <stdint.h> was way overdue) */ typedef uint16_t Elf32_Half; typedef int16_t Elf32_SHalf; diff -uNr klibc-0.178/include/sys/elf64.h klibc-0.178-fogo/include/sys/elf64.h --- klibc-0.178/include/sys/elf64....

...ull latest git pull git://git.debian.org/~maks/klibc.git maks forgot to ask to keep git port open for our boxes at university, thus moved my tree over too the alioth box. for the changes maximilian attems (4): [klibc] klibc/socketcalls/.gitignore addition [klibc] elf.h add support for st_info field [klibc] remove local insmod.c copy [klibc] ipconfig fix DHCPREQUEST per RFC 2131 the diffstat is usr/include/sys/elf32.h | 4 + usr/include/sys/elf64.h | 4 + usr/include/sys/elfcommon.h | 10 +++ usr/kinit/ipconfig/dhcp_proto.c | 2 +- usr/kli...

..."__sym_attr_metadata.<int>", that the linker can recognize when scanning the symbol table for an incoming object file. In an ELF symbol table entry: typedef struct { Elf32_Word st_name; Elf32_Addr st_value; Elf32_Word st_size; unsigned char st_info; unsigned char st_other; Elf32_Half st_shndx; } Elf32_Sym; typedef struct { Elf64_Word st_name; unsigned char st_info; unsigned char st_other; Elf64_Half st_shndx; Elf64_Addr st_value; Elf64_Xword st_size; } Elf64_Sym;...

...er can recognize when scanning the symbol table for an incoming object file. In an ELF symbol table entry: > > > > typedef struct { > > Elf32_Word st_name; > > Elf32_Addr st_value; > > Elf32_Word st_size; > > unsigned char st_info; > > unsigned char st_other; > > Elf32_Half st_shndx; > > } Elf32_Sym; > > > > typedef struct { > > Elf64_Word st_name; > > unsigned char st_info; > > unsigned char st_other; > > Elf64_Half...

...for an incoming object file. In an ELF symbol table entry: > > > > typedef struct { > > Elf32_Word st_name; > > Elf32_Addr st_value; > > Elf32_Word st_size; > > unsigned char st_info; > > unsigned char st_other; > > Elf32_Half st_shndx; > > } Elf32_Sym; > > > > typedef struct { > > Elf64_Word st_name; > > unsigned char st_info; > &gt...

...d to make this work. > Tell me more about the semantics of STT_FILE. The goal is not just to pass through ELF-isms. The goal is to define a really good model and translate each object format into that model. A web search for STT_FILE gives: > In this case for it may be an ELF'ism, when st_info == STB_LOCAL | STT_FILE st_shndx == SHN_ABS Then st_value will probably be zero and this symbol's name should match the name of the originating source file. Currently there is only one qualifying characteristic a symbol must have in order to be converted into an absolute atom, st_shndx == SH...

...the semantics of STT_FILE. The goal is not just to > pass through ELF-isms. The goal is to define a really good model and > translate each object format into that model. A web search for STT_FILE > gives: > >> > > In this case for it may be an ELF'ism, when > > st_info == STB_LOCAL | STT_FILE > > st_shndx == SHN_ABS > > > > Then st_value will probably be zero and this symbol's name should match > > the name of the originating source file. > The lld::File class has a method translationUnitSource() that (if > available) returns the...

.... >> Tell me more about the semantics of STT_FILE. The goal is not just to pass through ELF-isms. The goal is to define a really good model and translate each object format into that model. A web search for STT_FILE gives: >> > In this case for it may be an ELF'ism, when > st_info == STB_LOCAL | STT_FILE > st_shndx == SHN_ABS > > Then st_value will probably be zero and this symbol's name should match > the name of the originating source file. The lld::File class has a method translationUnitSource() that (if available) returns the path to the source file that...

...> > typedef struct { > > > > > > Elf32_Word st_name; > > > > > > Elf32_Addr st_value; > > > > > > Elf32_Word st_size; > > > > > > unsigned char st_info; > > > > > > unsigned char st_other; > > > > > > Elf32_Half st_shndx; > > > > > > } Elf32_Sym; > > > > > > > > > > > > typedef struct { > >...

...l me more about the semantics of STT_FILE. The goal is not just to pass through ELF-isms. The goal is to define a really good model and translate each object format into that model. A web search for STT_FILE gives: > >> > > In this case for it may be an ELF'ism, when > > st_info == STB_LOCAL | STT_FILE > > st_shndx == SHN_ABS > > > > Then st_value will probably be zero and this symbol's name should match > > the name of the originating source file. > The lld::File class has a method translationUnitSource() that (if available) returns the path...

...> > typedef struct { > > > > > > Elf32_Word st_name; > > > > > > Elf32_Addr st_value; > > > > > > Elf32_Word st_size; > > > > > > unsigned char st_info; > > > > > > unsigned char st_other; > > > > > > Elf32_Half st_shndx; > > > > > > } Elf32_Sym; > > > > > > > > > > > > typedef struct { > >...

...; > > Elf32_Word st_name; >> > > > >> > > > Elf32_Addr st_value; >> > > > >> > > > Elf32_Word st_size; >> > > > >> > > > unsigned char st_info; >> > > > >> > > > unsigned char st_other; >> > > > >> > > > Elf32_Half st_shndx; >> > > > >> > > > } Elf32_Sym; >> > > > >> > > &g...

...; > > > > > > Elf32_Word st_name; > > > > > > > > Elf32_Addr st_value; > > > > > > > > Elf32_Word st_size; > > > > > > > > unsigned char st_info; > > > > > > > > unsigned char st_other; > > > > > > > > Elf32_Half st_shndx; > > > > > > > > } Elf32_Sym; > > > > > > > > > > > > >...

On Oct 15, 2012, at 8:08 AM, Sidney Manning wrote: > > I think that absolute atoms will need something similar to, "contentType" added. > > SHN_ABS symbols can have different types, STT_OBJECT, STT_FILE and maybe others. In order for the writer to tell it must have a way to reach back and ask the atom what type of symbols caused it to be created. To that end I added a

I think that absolute atoms will need something similar to, "contentType" added. SHN_ABS symbols can have different types, STT_OBJECT, STT_FILE and maybe others. In order for the writer to tell it must have a way to reach back and ask the atom what type of symbols caused it to be created. To that end I added a contentType method to AbsoluteAtom and sprinkled changes around to

From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific

Hi Andi, Four patches: - clean up asm/bugs.h, by moving all the C code into its own C file - split identify_cpu() into boot and secondary variants, so that boot-time setup functions can be marked __init - repost of the COMPAT_VDSO patches with a bit more robustness from unknown DT_tags, and functions marked __init, since all this is boot-time only setup. Thanks, J --