Re: [PATCH v3] x86: Treat R_386_PLT32 as R_386_PC32

2021-01-25 Thread Fangrui Song
On 2021-01-25, Borislav Petkov wrote: It's a good thing I have a toolchain guy who can explain to me what you guys are doing because you need to start writing those commit messages for !toolchain developers. How about this following message? I'll answer your questions in line as well.

Re: [PATCH v3] x86: Treat R_386_PLT32 as R_386_PC32

2021-01-25 Thread Borislav Petkov
It's a good thing I have a toolchain guy who can explain to me what you guys are doing because you need to start writing those commit messages for !toolchain developers. On Thu, Jan 14, 2021 at 02:48:19PM -0800, Fangrui Song wrote: > This is similar to commit b21ebf2fb4cd ("x86: Treat

Re: [PATCH v3] x86: Treat R_386_PLT32 as R_386_PC32

2021-01-22 Thread Fāng-ruì Sòng
On Thu, Jan 14, 2021 at 2:48 PM Fangrui Song wrote: > > This is similar to commit b21ebf2fb4cd ("x86: Treat R_X86_64_PLT32 as > R_X86_64_PC32"), but for i386. As far as Linux kernel is concerned, > R_386_PLT32 can be treated the same as R_386_PC32. > > R_386_PC32/R_X86_64_PC32 are PC-relative

[PATCH v3] x86: Treat R_386_PLT32 as R_386_PC32

2021-01-14 Thread Fangrui Song
This is similar to commit b21ebf2fb4cd ("x86: Treat R_X86_64_PLT32 as R_X86_64_PC32"), but for i386. As far as Linux kernel is concerned, R_386_PLT32 can be treated the same as R_386_PC32. R_386_PC32/R_X86_64_PC32 are PC-relative relocation types with the requirement that the symbol address is