From: Michal Kubecek <mkubecek@suse.cz>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "'Hannes Frederic Sowa'" <hannes@stressinduktion.org>,
Fabian Frederick <fabf@skynet.be>,
Guenter Roeck <linux@roeck-us.net>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1 net-next] af_unix: remove NULL assignment on static
Date: Wed, 8 Oct 2014 11:46:20 +0200 [thread overview]
Message-ID: <20141008094620.GA12270@unicorn.suse.cz> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D174C6CA5@AcuExch.aculab.com>
On Wed, Oct 08, 2014 at 09:10:23AM +0000, David Laight wrote:
> From: Hannes Frederic Sowa
> > I think David's concern was whether if 0 == false in all situations. It
> > is pretty clear that static memory is initialized to 0.
>
> I'm not 100% sure about that.
> static pointers may be required to be initialised to NULL.
ISO C 99 says:
If an object that has static storage duration is not initialized
explicitly, then:
- if it has pointer type, it is initialized to a null pointer;
- if it has arithmetic type, it is initialized to (positive or
unsigned) zero;
- if it is an aggregate, every member is initialized (recursively)
according to these rules;
- if it is a union, the first named member is initialized
(recursively) according to these rules.
Michal Kubeček
prev parent reply other threads:[~2014-10-08 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 20:16 [PATCH 1/1 net-next] af_unix: remove NULL assignment on static Fabian Frederick
2014-10-07 20:18 ` David Miller
2014-10-07 20:26 ` Hannes Frederic Sowa
2014-10-07 20:33 ` Guenter Roeck
2014-10-07 20:49 ` Fabian Frederick
2014-10-07 20:50 ` David Miller
2014-10-07 20:54 ` Hannes Frederic Sowa
2014-10-07 21:05 ` Fabian Frederick
2014-10-08 9:10 ` David Laight
2014-10-08 9:34 ` Hannes Frederic Sowa
2014-10-08 9:46 ` Michal Kubecek [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=20141008094620.GA12270@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=fabf@skynet.be \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.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