Re: Linux 4.18-rc7

From: youling 257
Date: Tue Jul 31 2018 - 18:57:47 EST


Build fingerprint: 'Android-x86/android_x86/x86:8.1.0/OPM6.171019.030.B1/cwhuang0618:userdebug/test-keys'
Revision: '0'
ABI: 'x86'
pid: 2899, tid: 2899, name: zygote >>> zygote <<<
signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 0xec00008
  eax 00000000 ebx f0274a40 ecx 000001e0 edx 0ec00008
  esi 00000000 edi 0ec00000
  xcs 00000023 xds 0000002b xes 0000002b xfs 00000003 xss 0000002b
  eip f24a4996 ebp ffc4eaa8 esp ffc4ea68 flags 00010202

backtrace:
  #00 pc 0001a996 /system/lib/libc.so (memset+150)
  #01 pc 0022b2be /system/lib/libart.so (create_mspace_with_base+222)
  #02 pc 002b2a05 /system/lib/libart.so (art::gc::space::DlMallocSpace::CreateMspace(void*, unsigned int, unsigned int)+69)
  #03 pc 002b2637 /system/lib/libart.so (art::gc::space::DlMallocSpace::CreateFromMemMap(art::MemMap*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, unsigned int, unsigned int, unsigned int, unsigned int, bool)+55)
  #04 pc 0027f6af /system/lib/libart.so (art::gc::Heap::Heap(unsigned int, unsigned int, unsigned int, unsigned int, double, double, unsigned int, unsigned int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, art::InstructionSet, art::gc::CollectorType, art::gc::CollectorType, art::gc::space::LargeObjectSpaceType, unsigned int, unsigned int, unsigned int, bool, unsigned int, unsigned int, bool, bool, bool, bool, bool, bool, bool, bool, bool, bool, bool, unsig #05 pc 0055a17a /system/lib/libart.so (_ZN3art7Runtime4InitEONS_18RuntimeArgumentMapE+11434)
  #06 pc 0055e928 /system/lib/libart.so (art::Runtime::Create(std::__1::vector<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>, void const*>, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>, void const*>>> const&, bool)+184)

2018-08-01 0:29 GMT+08:00 Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>:
On Mon, Jul 30, 2018 at 11:40 PM Amit Pundir <amit.pundir@xxxxxxxxxx> wrote:
>
> This ashmem change ^^ worked too.

Ok, let's go for that one and hope it's the only one.

John, can I get a proper commit message and sign-off for that ashmem change?

Kirill - you mentioned that somebody reproduced a problem on x86-64
too. I didn't see that report. Was that some odd x86 Android setup
with Ashmem too, or is there something else pending?

           ÂLinus