From: Eric Dumazet <eric.dumazet@gmail.com>
To: Joe Perches <joe@perches.com>, David Miller <davem@davemloft.net>,
thierry.reding@gmail.com
Cc: hkallweit1@gmail.com, andrew@lunn.ch, nic_swsd@realtek.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] r8169: Avoid pointer aliasing
Date: Tue, 5 Feb 2019 12:23:18 -0800 [thread overview]
Message-ID: <efc77e73-914b-3b9b-16f2-1ca5353f5210@gmail.com> (raw)
In-Reply-To: <4aea523a3bc5be0d944f7ed9fadac276b7115002.camel@perches.com>
On 02/05/2019 12:18 PM, Joe Perches wrote:
> I still think adding __align(<even#>) is unnecessary here unless
> it follows something like a bool or a u8.
This would be some historical side effect, and we do not want to rely on that.
A security feature could in fact ask a compiler to perform random
shuffling of automatic variables.
( a la __randomize_layout )
next prev parent reply other threads:[~2019-02-05 20:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 16:42 [PATCH v2 1/2] r8169: Load MAC address from device tree if present Thierry Reding
2019-02-04 16:42 ` [PATCH v2 2/2] r8169: Avoid pointer aliasing Thierry Reding
2019-02-04 16:59 ` Andrew Lunn
2019-02-04 18:44 ` Heiner Kallweit
2019-02-05 3:20 ` David Miller
2019-02-05 18:42 ` Joe Perches
2019-02-05 19:14 ` David Miller
2019-02-05 19:19 ` Joe Perches
2019-02-06 7:25 ` Michal Kubecek
2019-02-05 20:04 ` Eric Dumazet
2019-02-05 20:18 ` Joe Perches
2019-02-05 20:23 ` Eric Dumazet [this message]
2019-02-05 20:23 ` Heiner Kallweit
2019-02-04 19:30 ` [PATCH v2 1/2] r8169: Load MAC address from device tree if present Heiner Kallweit
2019-02-06 2:27 [PATCH v2 2/2] r8169: Avoid pointer aliasing Paul Zimmerman
2019-02-06 2:52 ` Joe Perches
2019-02-06 3:25 ` Paul Zimmerman
2019-02-06 3:49 ` Joe Perches
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=efc77e73-914b-3b9b-16f2-1ca5353f5210@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).