Btw, the attachment is lost, but I assume it is the same problem. On Thu, Oct 26, 2017 at 11:17 AM, Evgenii Stepanov <[email protected]> wrote: > Yes. 32-base base is still a problem specifically on Android. The best > option is to revert it, too. We are also investigating a fix on the > ASan side. > > On Thu, Oct 26, 2017 at 7:59 AM, 'Dmitry Vyukov' via address-sanitizer > <[email protected]> wrote: >> Hi, >> >> I am missing some context. >> How can this be reproduced? What is the user-space program? Is it >> built with gcc or clang? What version? Does it require some special >> kernel? What exactly? >> >> >> >> On Wed, Oct 25, 2017 at 7:17 PM, Olav Haugan <[email protected]> wrote: >>> Hi Kees/Kostya/Dmitry, >>> >>> Have you been able to reproduce this? >>> >>> Thanks, >>> >>> Olav >>> >>>> >>>> Hi Kees, >>>> >>>> Thanks for looking into it. Yeah, I think the 32 bit base is still an >>>> issue. >>>> >>>> > >>>> > I see this in the log: >>>> > >>>> > 01-01 00:06:46.743 658 658 I : ==658==ASan shadow was >>>> > supposed to be located in the [0x00000000-0x1fffffff] range. >>>> > >>>> > I've CCed Kostya and Dmitry who should be able to help track this >>>> > down. The upstream revert left the 32-bit base alone since they'd said >>>> > it wasn't a problem. Perhaps it still is in some way? >>>> > >>>> > -Kees >>>> > >>>> > On Fri, Sep 29, 2017 at 1:28 AM, Olav Haugan <[email protected]> wrote: >>>> > > Hi Kees, >>>> > > >>>> > > We are having issue booting our devices due to the "binfmt_elf: use >>>> > ELF_ET_DYN_BASE only for PIE" and "arm64: move ELF_ET_DYN_BASE to 4GB >>>> / >>>> > 4MB" patches. We tried applying the partial revert of these with [1] but >>>> > we are >>>> > still running into issues. It appears that 32 bit processes are having >>>> > an issue. >>>> > Logcat attached. >>>> > > >>>> > > Have you seen this issue yet? The only solution we have so far is to >>>> > > do a >>>> > complete revert of above mentioned changes. >>>> > > >>>> > > [1] https://patchwork.kernel.org/patch/9886105/ >>>> > > >>>> > > Thanks, >>>> > > >>>> > > -- >>>> > > Olav >>>> > > >>>> > >>>> > >>>> > >>>> > -- >>>> > Kees Cook >>>> > Pixel Security >> >> -- >> You received this message because you are subscribed to the Google Groups >> "address-sanitizer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
