From: Al Viro <viro@ZenIV.linux.org.uk>
To: David Miller <davem@davemloft.net>
Cc: ben@decadent.org.uk, luis.henriques@canonical.com,
avijitnsec@codeaurora.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: CVE-2014-9900 fix is not upstream
Date: Tue, 23 Aug 2016 21:09:41 +0100 [thread overview]
Message-ID: <20160823200941.GB2356@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160823.112406.549221808236512285.davem@davemloft.net>
On Tue, Aug 23, 2016 at 11:24:06AM -0700, David Miller wrote:
> > On some versions and architectures. Can you guarantee that you will
> > notice when an exception appears?
>
> Again, show me the assembler output exhibiting the lack of
> initialization, for this specific structure and situation.
>
> That's all that I'm asking.
... and then we can file a bug report against the sodding compiler. Note
that
struct ethtool_wolinfo {
__u32 cmd;
__u32 supported;
__u32 wolopts;
__u8 sopass[SOPASS_MAX]; // 6, actually
};
is not going to *have* padding. Not on anything even remotely sane.
If array of 6 char as member of a struct requires 64bit alignment on some
architecture, I would really like some of what the designers of that ABI
must have been smoking.
Initializer might be allowed to leave padding uninitialized. But all fields
_must_ be initialized, the missing initializers treated exactly as they
would've been for a static-duration object (C99 6.7.8p19). And that is
going to cover everything in that sucker. It's not a function of compiler -
only of C ABI on given target.
next prev parent reply other threads:[~2016-08-23 20:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 13:41 CVE-2014-9900 fix is not upstream Luis Henriques
2016-08-23 13:41 ` net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol() Luis Henriques
2016-08-23 14:06 ` Joe Perches
[not found] ` <CAOp4FwRxfE61azV78TZ7EKESQZzRU2Pfkc2GJ9j3MV7pr80qew@mail.gmail.com>
2016-08-23 15:40 ` Joe Perches
2016-08-23 14:21 ` Eric Dumazet
2016-08-23 15:05 ` Joe Perches
2016-08-23 15:36 ` Eric Dumazet
2016-08-23 16:38 ` Andrey Ryabinin
2016-08-23 16:46 ` Edward Cree
2016-08-23 17:15 ` Vegard Nossum
2016-08-23 17:33 ` Ben Hutchings
2016-08-23 16:40 ` CVE-2014-9900 fix is not upstream David Miller
2016-08-23 17:35 ` Ben Hutchings
2016-08-23 18:24 ` David Miller
2016-08-23 20:09 ` Al Viro [this message]
2016-08-23 20:34 ` Joe Perches
2016-08-23 20:49 ` Lennart Sorensen
2016-08-23 21:25 ` Al Viro
2016-08-24 14:03 ` Lennart Sorensen
2016-08-24 20:36 ` Hannes Frederic Sowa
2016-08-25 12:40 ` Johannes Berg
2016-08-25 12:41 ` Johannes Berg
2016-08-25 15:14 ` One Thousand Gnomes
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=20160823200941.GB2356@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=avijitnsec@codeaurora.org \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--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