public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: tdm@sgi.com, xfs@oss.sgi.com, Jan Kara <jack@suse.com>
Subject: Re: [PATCH] xfs: Fix xfs_attr_leafblock definition
Date: Tue, 18 Aug 2015 09:57:55 +1000	[thread overview]
Message-ID: <20150817235755.GE714@dastard> (raw)
In-Reply-To: <55CC98DD.6060700@sgi.com>

On Thu, Aug 13, 2015 at 08:17:17AM -0500, Mark Tinguely wrote:
> On 08/13/15 04:26, Jan Kara wrote:
> >struct xfs_attr_leafblock contains 'entries' array which is declared
> >with size 1 altough it can in fact contain much more entries. Since this
> >array is followed by further struct members, gcc (at least in version
> >4.8.3) thinks that the array has the fixed size of 1 element and thus
> >may optimize away all accesses beyond the end of array resulting in
> >non-working code. This problem was only observed with userspace code in
> >xfsprogs, however it's better to be safe in kernel as well and have
> >matching kernel and xfsprogs definitions.
> >
> >Signed-off-by: Jan Kara<jack@suse.com>
> >---
> 
> I hit this bug in SLES12 and RHEL7 XFS kernel code. It is the gcc
> 4.8's new loop optimization routine. A person can bypass it with the
> option:
>     -fno-aggressive-loop-optimizations
> but this fixes the source of the problem.
> 
> Acked-by: Mark Tinguely <tinguely@sgi.com>

Hi Mark - it's great that you had found and identified the exact
compiler optimisation that was causing miscompilation of the XFS
code.

Troy, what's not great about this is that SGI hasn't seen fit to
report this bug upstream or to their distro partners in a prompt
manner. Can you please make sure that any other XFS bug fixes that
SGI are sitting on get communicated to the appropriate venue so
they can be addressed without undue delay?

Thanks,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-08-17 23:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13  9:26 [PATCH] xfs: Fix xfs_attr_leafblock definition Jan Kara
2015-08-13 13:17 ` Mark Tinguely
2015-08-17 23:57   ` Dave Chinner [this message]
2015-08-14  3:02 ` Eric Sandeen

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=20150817235755.GE714@dastard \
    --to=david@fromorbit.com \
    --cc=jack@suse.com \
    --cc=tdm@sgi.com \
    --cc=tinguely@sgi.com \
    --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