linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dirk.behme@gmail.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: fix memset-related crashes caused by recent GCC (4.7.2) optimizations
Date: Wed, 26 Feb 2014 18:13:15 +0100	[thread overview]
Message-ID: <530E20AB.80301@gmail.com> (raw)
In-Reply-To: <CAGVrzcaAGqWG4-fiVc+YiPms5aqSkoXBMmK4rR=wr9XQJ083jw@mail.gmail.com>

Am 26.02.2014 01:43, schrieb Florian Fainelli:
> 2013-03-12 3:06 GMT-07:00 Alexander Holler <holler@ahsoftware.de>:
>>
>> Tested-by: Alexander Holler
>>
>> It works since 2 days on my busy 24/7 armv5-thingy without me having seen an
>> error. A quick test on an armv7-system hasn't revealed any problems too.
>
> This is an old thread, but 3.8.13 is still affected, not quite sure if
> there will be a 3.8.14 release, but if there is, we should
> definitively get:
>
> ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2)
> optimizations
> ARM: 7670/1: fix the memset fix
>
> included in 3.8.14.

Ubuntu is continuing support for some kernels with -stable patches:

https://lwn.net/Articles/550581/

http://kernel.ubuntu.com/git?p=ubuntu/linux.git

Having a short check in v3.8.13.18, this patch is not included there, 
yet. Maybe you want to ask them if they want to include it.

Best regards

Dirk

      reply	other threads:[~2014-02-26 17:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 12:57 [PATCH v2] arm: fix memset-related crashes caused by recent GCC (4.7.2) optimizations Ivan Djelic
2013-03-06 19:15 ` Dirk Behme
2013-03-07  8:13   ` Ivan Djelic
2013-03-07 15:17   ` Russell King - ARM Linux
2013-03-10 17:06     ` Alexander Holler
2013-03-10 17:28       ` Russell King - ARM Linux
2013-03-10 17:41         ` Alexander Holler
2013-03-10 18:46         ` Nicolas Pitre
2013-03-10 19:23           ` Nicolas Pitre
2013-03-10 20:46         ` Ivan Djelic
2013-03-11  4:10         ` Nicolas Pitre
2013-03-12 10:06           ` Alexander Holler
2014-02-26  0:43             ` Florian Fainelli
2014-02-26 17:13               ` Dirk Behme [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530E20AB.80301@gmail.com \
    --to=dirk.behme@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).