From: Dave Chinner <david@fromorbit.com>
To: Yann Dupont - Veille Techno <veilletechno-irts@univ-nantes.fr>
Cc: xfs@oss.sgi.com
Subject: Re: xfstests, bad generic tests 009 and 308
Date: Thu, 24 Sep 2015 08:04:44 +1000 [thread overview]
Message-ID: <20150923220444.GP19114@dastard> (raw)
In-Reply-To: <56028249.7040103@univ-nantes.fr>
On Wed, Sep 23, 2015 at 12:43:21PM +0200, Yann Dupont - Veille Techno wrote:
> Le 22/09/2015 00:52, Dave Chinner a écrit :
> >As it is, I highly recommend that you try a current 4.3 kernel, as
> >there are several code fixes in the XFS kernel code that work
> >around compiler issues we know about. AFAIA, the do_div() asm bug
> >that trips recent gcc optimisations isn't in the upstream kernel
> >yet, but that can be worked around by setting
> >CONFIG_CC_OPTIMIZE_FOR_SIZE=y in your build.
>
> Hi dave,
>
> I can confirm that CONFIG_CC_OPTIMIZE_FOR_SIZE=y is (was ?) the only
> way for me to have reliable XFS kernel code on different arm
> platforms (Marvell kirkwood, Allwinner A20, Amlogic S805), no matter
> what recent gcc version I've been using.
>
> I must admit I was cross-compiling from X86-64 too, but I think (not
> sure) that it was also the case with native gcc.
>
> I must also admit that I didn't tried since some months, because
> CONFIG_CC_OPTIMIZE_FOR_SIZE=y was the silver bullet for arm xfs
> kernel crashes. This crash was difficult to understand because it
> occurs quite randomly (I.e it can take several hours to trigger)
>
> If there's a patch floating around for gcc (or kernel), I'm
> interested to test.
See this subthread from august:
http://oss.sgi.com/archives/xfs/2015-08/msg00234.html
AFAICT, the do_div patch to fix the problem has not yet been picked
up - it's not in the 4.3-rc2 kernel...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-23 22:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 16:38 xfstests, bad generic tests 009 and 308 Angelo Dureghello
2015-09-18 22:44 ` Dave Chinner
2015-09-21 11:13 ` Angelo Dureghello
2015-09-21 11:18 ` Angelo Dureghello
2015-09-21 22:52 ` Dave Chinner
2015-09-22 12:41 ` Angelo Dureghello
2015-09-22 21:27 ` Dave Chinner
2015-09-23 9:15 ` Angelo Dureghello
2015-09-23 22:25 ` Dave Chinner
2015-09-23 10:43 ` Yann Dupont - Veille Techno
2015-09-23 22:04 ` Dave Chinner [this message]
2015-09-24 8:20 ` Yann Dupont - Veille Techno
2015-09-27 0:40 ` Angelo Dureghello
-- strict thread matches above, loose matches on Subject: below --
2015-09-18 16:16 angelo
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=20150923220444.GP19114@dastard \
--to=david@fromorbit.com \
--cc=veilletechno-irts@univ-nantes.fr \
--cc=xfs@oss.sgi.com \
/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