From: Stephen Hemminger <stephen@networkplumber.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>, <ying.xue@windriver.com>,
<steffen.klassert@secunet.com>, <dborkman@redhat.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: xfrm6: silence sparse warning
Date: Thu, 9 Jan 2014 21:30:22 -0800 [thread overview]
Message-ID: <20140109213022.7e6f8921@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1389322386.2728.66.camel@deadeye.wl.decadent.org.uk>
On Fri, 10 Jan 2014 02:53:06 +0000
Ben Hutchings <bhutchings@solarflare.com> wrote:
> On Thu, 2014-01-09 at 15:04 -0800, Stephen Hemminger wrote:
> > On Wed, 08 Jan 2014 00:56:56 -0500 (EST)
> > David Miller <davem@davemloft.net> wrote:
> >
> > > From: Ying Xue <ying.xue@windriver.com>
> > > Date: Wed, 8 Jan 2014 13:55:09 +0800
> > >
> > > > 3. Just drop the patch
> > >
> > > This is the only suitable thing to do.
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe netdev" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> > There was some patches floating around to eliminate uses of variable
> > length array in the kernel since they aren't supported by CLANG.
>
> I think you're mixing up two different things there. VLAs are part of
> C99 so I'm quite sure Clang supports them (in general). But they seem
> to be deprecated in the kernel anyway, maybe because they make it easy
> to introduce a stack overflow.
>
> Ben.
>
Reading up on this, the problem in CLANG is VLA in Structs;
as in:
struct foo {
char a[n];
int b;
};
next prev parent reply other threads:[~2014-01-10 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 2:56 [PATCH net-next] net: xfrm6: silence sparse warning Ying Xue
2014-01-08 3:43 ` David Miller
2014-01-08 5:55 ` Ying Xue
2014-01-08 5:56 ` David Miller
2014-01-09 23:04 ` Stephen Hemminger
2014-01-10 2:53 ` Ben Hutchings
2014-01-10 5:30 ` Stephen Hemminger [this message]
2014-01-08 20:46 ` Ben Hutchings
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=20140109213022.7e6f8921@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=ying.xue@windriver.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 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.