From: Anton Blanchard <anton@ozlabs.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
linux-ext4@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext4: fix warning about stack corruption
Date: Tue, 22 Aug 2017 22:23:13 +1000 [thread overview]
Message-ID: <20170822222313.468ee7aa@kryten> (raw)
In-Reply-To: <CAK8P3a05GOh87tGhnuUS_gYmQVjgTrC-e58KagVPG4hHSuFTgg@mail.gmail.com>
> > Unfortunately it doesn't appear to work, at least with ppc64le
> > clang:
> >
> > fs/ext4/mballoc.c:2303:17: error: fields must have a constant size:
> > 'variable length array in structure' extension will never be
> > supported ext4_grpblk_t counters[blocksize_bits + 2];
>
> My fix for this is in the ext4/dev branch in linux-next, I hope it
> still makes it into v4.13.
Thanks Arnd, I see it now.
Anton
prev parent reply other threads:[~2017-08-22 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 18:52 [PATCH v2] fortify: Use WARN instead of BUG for now Kees Cook
2017-07-26 19:55 ` Josh Poimboeuf
2017-07-26 21:33 ` Kees Cook
2017-07-29 8:56 ` kbuild test robot
2017-08-01 12:04 ` [PATCH 1/2] ext4: fix warning about stack corruption Arnd Bergmann
2017-08-01 12:04 ` [PATCH 2/2] adfs: use 'unsigned' types for memcpy length Arnd Bergmann
2017-08-01 18:20 ` Kees Cook
2017-08-01 21:43 ` Stephen Rothwell
2017-08-01 18:26 ` [PATCH 1/2] ext4: fix warning about stack corruption Kees Cook
2017-08-06 1:53 ` Theodore Ts'o
2017-08-06 20:34 ` Arnd Bergmann
2017-08-07 6:42 ` Chandan Rajendra
2017-08-22 11:08 ` Anton Blanchard
2017-08-22 11:57 ` Arnd Bergmann
2017-08-22 12:23 ` Anton Blanchard [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=20170822222313.468ee7aa@kryten \
--to=anton@ozlabs.org \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=chandan@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.