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

Groups > linux.debian.kernel > #58125 > unrolled thread

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

Started byXimin Luo <infinity0@debian.org>
First post2017-06-22 19:10 +0200
Last post2017-07-04 13:40 +0200
Articles 6 — 3 participants

Back to article view | Back to linux.debian.kernel

Contents

  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

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

FromXimin Luo <infinity0@debian.org>
Date2017-06-22 19:10 +0200
SubjectBug#865549: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el
Message-ID<tVdMe-7Ei-21@gated-at.bofh.it>
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.

Thanks,
Ximin

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[toc] | [next] | [standalone]

#58133

FromBen Hutchings <ben@decadent.org.uk>
Date2017-06-22 23:40 +0200
Message-ID<tVhZv-1Jh-1@gated-at.bofh.it>
In reply to#58125

[Multipart message — attachments visible in raw view] — view raw

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.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.

[toc] | [prev] | [next] | [standalone]

#58135

FromXimin Luo <infinity0@debian.org>
Date2017-06-23 02:10 +0200
Message-ID<tVkkF-3iz-1@gated-at.bofh.it>
In reply to#58133
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

[toc] | [prev] | [next] | [standalone]

#58134 — Processed: Re: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el

Fromowner@bugs.debian.org (Debian Bug Tracking System)
Date2017-06-22 23:40 +0200
SubjectProcessed: Re: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el
Message-ID<tVhZv-1Jh-11@gated-at.bofh.it>
In reply to#58125
Processing control commands:

> tag -1 moreinfo
Bug #865549 [src:linux] linux: stack-guard fix for CVE-2017-1000364 incorrect
Added tag(s) moreinfo.

-- 
865549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865549
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#58136 — Processed (with 1 error): Re: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el

Fromowner@bugs.debian.org (Debian Bug Tracking System)
Date2017-06-23 09:20 +0200
SubjectProcessed (with 1 error): Re: linux-image-3.16.0-4-powerpc64le: stackguard fix incorrect; probably causes cargo to segfault on ppc64el
Message-ID<tVr2O-7yl-25@gated-at.bofh.it>
In reply to#58125
Processing control commands:

> forcemerge -1 865416
Bug #865549 [src:linux] linux: stack-guard fix for CVE-2017-1000364 incorrect
Unable to merge bugs because:
package of #865416 is 'cargo' not 'src:linux'
Failed to forcibly merge 865549: Did not alter merged bugs.


-- 
865416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865416
865549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865549
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#58259 — Processed: Re: [Pkg-rust-maintainers] Bug#865549: cargo still segfaults / rustc still FTBFS with the newest fixed kernel

Fromowner@bugs.debian.org (Debian Bug Tracking System)
Date2017-07-04 13:40 +0200
SubjectProcessed: Re: [Pkg-rust-maintainers] Bug#865549: cargo still segfaults / rustc still FTBFS with the newest fixed kernel
Message-ID<tZuls-7Dd-15@gated-at.bofh.it>
In reply to#58125
Processing control commands:

> tag -1 upstream patch moreinfo
Bug #865549 [src:linux] cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc
Bug #865416 [src:linux] cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc
Bug #866185 [src:linux] cargo ppc64el segfaults in recent (>June 20) kernels, causing FTBFS for rustc
Added tag(s) moreinfo and upstream.
Added tag(s) upstream and moreinfo.
Added tag(s) upstream and moreinfo.

-- 
865416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865416
865549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865549
866185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866185
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web