[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2TXPfFpgy+XjpDzOqt1qpDxufwiD-BLNbn4W_jpGp98g@mail.gmail.com>
Date: Thu, 7 Jan 2021 14:16:25 +0100
From: Arnd Bergmann <arnd@...nel.org>
To: Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc: Will Deacon <will@...nel.org>, linux-toolchains@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
"Theodore Ts'o" <tytso@....edu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Ext4 Developers List <linux-ext4@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Aarch64 EXT4FS inode checksum failures - seems to be weak memory
ordering issues
On Thu, Jan 7, 2021 at 1:47 PM Russell King - ARM Linux admin
<linux@...linux.org.uk> wrote:
> Arnd has found via bisecting gcc:
>
> 7e8c2bd54af ("[AArch64] fix unsafe access to deallocated stack")
>
> which seems to be https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63293
>
> That seems to suggest that gcc-5.0.0 is also affected.
>
> Looking at the changelog in Debian's gcc-8.3 packages, this doesn't
> feature, so it's not easy just to look at the changelogs to work out
> which versions are affected.
I checked the history to confirm that all gcc-5 releases (5.0.x is pre-release)
and later have the fix.
The gcc bugzilla mentions backports into gcc-linaro, but I do not see
them in my git history.
Arnd
Powered by blists - more mailing lists