Re: [RFC] kexec_file: Add support for purgatory built as PIE

2016-11-04 Thread Thiago Jung Bauermann
Hello Eric, Am Freitag, 4. November 2016, 10:13:39 BRST schrieb Eric W. Biederman: > Baoquan He writes: > > On 11/02/16 at 04:00am, Thiago Jung Bauermann wrote: > >> Hello, > >> > >> The kexec_file code currently builds the purgatory as a partially linked > >> object (using ld

Re: [RFC] kexec_file: Add support for purgatory built as PIE

2016-11-04 Thread Thiago Jung Bauermann
Hello Baoquan, Am Freitag, 4. November 2016, 15:38:40 BRST schrieb Baoquan He: > On 11/02/16 at 04:00am, Thiago Jung Bauermann wrote: > > Hello, > > > > The kexec_file code currently builds the purgatory as a partially linked > > object (using ld -r). Is there a particular reason to use that

Re: [RFC] kexec_file: Add support for purgatory built as PIE

2016-11-04 Thread Eric W. Biederman
Baoquan He writes: > On 11/02/16 at 04:00am, Thiago Jung Bauermann wrote: >> Hello, >> >> The kexec_file code currently builds the purgatory as a partially linked >> object >> (using ld -r). Is there a particular reason to use that instead of a >> position >> independent

Re: [RFC] kexec_file: Add support for purgatory built as PIE

2016-11-04 Thread Baoquan He
On 11/02/16 at 04:00am, Thiago Jung Bauermann wrote: > Hello, > > The kexec_file code currently builds the purgatory as a partially linked > object > (using ld -r). Is there a particular reason to use that instead of a position > independent executable (PIE)? It's taken as "-r", relocatable

[RFC] kexec_file: Add support for purgatory built as PIE

2016-11-02 Thread Thiago Jung Bauermann
Hello, The kexec_file code currently builds the purgatory as a partially linked object (using ld -r). Is there a particular reason to use that instead of a position independent executable (PIE)? I found a discussion from 2013 in the archives but from what I understood it was about the