Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #58135

Bug#865549: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el

Cross-posted to 2 groups.

Show all headers | View raw

jrtc27 graciously lent me access to a VM so I'm building it now and will test it some time tomorrow.

X

Ximin Luo:
> Hi, unfortunately I don't have root access to any ppc64el machines to be able to install a new kernel, I only have access to plummer.debian.org. (Also you didn't build them for ppc64el yet.)
> 
> There are some things different about what we're seeing in cargo, vs the provided C code that segfaults. However the timing is too coincidental so I'm still inclined to think it's caused by this bug. But unfortunately I don't know how I can test this myself.
> 
> Could you release this to stable so that I can ask the buildd people to install this on plummer, so I can test it?
> 
> Or, if anyone else is able to test it, you can download and extract this: https://static.rust-lang.org/dist/rust-1.18.0-powerpc64le-unknown-linux-gnu.tar.gz then run `for i in {1..10}; do rust-1.18.0-powerpc64le-unknown-linux-gnu/cargo/bin/cargo -V; done` and see if it segfaults.
> 
> X
> 
> Ben Hutchings:
>> Control: tag -1 moreinfo
>>
>> On Thu, 22 Jun 2017 19:02:26 +0200 Ximin Luo <infinity0@debian.org>
>> wrote:
>>> Package: linux-image-3.16.0-4-powerpc64le
>>> Version: 3.16.43-2+deb8u1
>>> Severity: critical
>>> Justification: breaks unrelated software
>>>  
>>> Dear Maintainer,
>>>  
>>> I have been getting segfaults trying to build cargo on ppc64el
>>>  
>>> https://github.com/rust-lang/cargo/issues/4197
>>>  
>>> The signs point to the recent stack guard fix as being the culprit, I can
>>> confirm that the test program given here:
>>>  
>>> http://www.openwall.com/lists/oss-security/2017/06/22/6
>>>  
>>> indicates the presence of the bug on plummer.debian.org. I'm not very familiar
>>> with kernel development so I don't know where the proper fix is, but subsequent
>>> discussion on that thread suggests that mainline has the "correct fix" whereas
>>> some distros applied an incorrect one.
>>
>> Can you please test with this candidate fix?
>> https://people.debian.org/~benh/packages/CVE-2017-1000364/
>>
>> Ben.
>>
> 
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#865549: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el Ximin Luo <infinity0@debian.org> - 2017-06-22 19:10 +0200
  Bug#865549: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el Ben Hutchings <ben@decadent.org.uk> - 2017-06-22 23:40 +0200
    Bug#865549: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el Ximin Luo <infinity0@debian.org> - 2017-06-23 02:10 +0200
  Processed: Re: linux-image-3.16.0-4-powerpc64le: stackguard fix  incorrect; probably causes cargo to segfault on ppc64el owner@bugs.debian.org (Debian Bug Tracking System) - 2017-06-22 23:40 +0200
  Processed (with 1 error): Re: linux-image-3.16.0-4-powerpc64le:  stackguard fix incorrect; probably causes cargo to segfault on ppc64el owner@bugs.debian.org (Debian Bug Tracking System) - 2017-06-23 09:20 +0200
  Processed: Re: [Pkg-rust-maintainers] Bug#865549: cargo still  segfaults / rustc still FTBFS with the newest fixed kernel owner@bugs.debian.org (Debian Bug Tracking System) - 2017-07-04 13:40 +0200

csiph-web