Bug#891249: linux: unstable kernel/data corruption on ppc64el

From	Aurelien Jarno <aurel32@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#891249: linux: unstable kernel/data corruption on ppc64el
Date	2018-02-26 15:20 +0100
Message-ID	<vnrNf-7J0-1@gated-at.bofh.it> (permalink)
References	<vmqJz-841-1@gated-at.bofh.it> <vnrDA-7EM-25@gated-at.bofh.it> <vmqJz-841-1@gated-at.bofh.it> <vnrDA-7EM-25@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

tag 891249 + fixed-upstream
thanks

On 2018-02-26 11:01, Breno Leitao wrote:
> Hi,
> 
> On 02/23/2018 03:52 PM, Aurelien Jarno wrote:
> 
> > DSA has installed the latest security kernel (4.9.82-1+deb9u2) on the
> > Debian POWER8 machines running ppc64el. While they boot correctly, then
> > programs segfault randomly (apt, sbuild, systemd, etc...). Passing
> > no_rfi_flush to the command line does not change anything. Looking more
> > in details, things looks scarying as some code actually get wrongly
> > executed. Here are some build logs examples:
> > - https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519399908&raw=0
> > - https://buildd.debian.org/status/fetch.php?pkg=python-msgpack&arch=ppc64el&ver=0.5.1-1&stamp=1519396907&raw=0
> > - https://buildd.debian.org/status/fetch.php?pkg=tk8.5&arch=ppc64el&ver=8.5.19-3&stamp=1519362938&raw=0
> > 
> > While in the above case the packages fail to build from source, I guess
> > there are also some cases of undetected corruptions.
> > 
> > I'll try to run the 4.9.80-2 kernel at some point to narrow down the
> > issue.
> 
> I talked to the powerpc maintainer about this problem, and in fact this is a knew
> problem, since the 4.4 patches were 'backported' to 4.9 without success.
> 
> This is already fixed and in the stable tree already:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/arch/powerpc?h=linux-4.9.y
> 
> I understand that the commit ids are:
>  * 3146a32b39cd78722869bca6e839b3c59155e012
>  * efe8bc07c47fff196bbc0822e249a27ae0574d24
>  * ec0084d082137b73460303b39f4089970a213ad7
> 
> But I suppose that Debian will do a full merge with the stable tree, then, I expect
> that the next release will just work.

Thanks for the quick answer. I confirm that these commit are indeed in
the 4.9.84 stable release, which has been released yesterday. I guess
3146a32b39cd78722869bca6e839b3c59155e012 is the one which fixes the data
corruption.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

Thread

Bug#891249: linux: unstable kernel/data corruption on ppc64el Aurelien Jarno <aurel32@debian.org> - 2018-02-23 20:00 +0100
  Bug#891249: linux: unstable kernel/data corruption on ppc64el Aurelien Jarno <aurel32@debian.org> - 2018-02-26 15:20 +0100
    Processed: Re: Bug#891249: linux: unstable kernel/data corruption  on ppc64el "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-02-26 15:30 +0100
  Bug#891249: marked as done (linux: unstable kernel/data  corruption on ppc64el) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-03-03 12:10 +0100

csiph-web