Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Alexey Brodkin' <Alexey.Brodkin@synopsys.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"greg@kroah.com" <greg@kroah.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [RESEND PATCH v2] devres: Really align data field to unsigned long long
Date: Mon, 9 Jul 2018 10:18:36 +0000	[thread overview]
Message-ID: <91c57eeba2134dd99a9f0e11fa883c7c@AcuMS.aculab.com> (raw)
In-Reply-To: <c95ac7435736d93843c45628ba4d41a4a4988074.camel@synopsys.com>

From: Alexey Brodkin
> Sent: 09 July 2018 11:00
...
> That's a good idea indeed but it doesn't solve the problem with
> struct devres_node. Consider the following snippet:
> -------------------------------->8-------------------------------
> 	struct mystruct {
> 		atomic64_t myvar;
> 	}
> 
> 	struct mystruct *p;
> 	p = devm_kzalloc(dev, sizeof(*p), GFP_KERNEL);
> -------------------------------->8-------------------------------
> 
> Here myvar address will match address of "data" member of struct devres_node.
> So if "data" is has offset of 12 bytes from the beginning of a page then
> myvar won't be 64-bit aligned regardless of myvar's attribute, right?
...
> > > -	unsigned long long		data[];	/* guarantee ull alignment */

Ahh, that line should be:
	u8 data[] __aligned(8); /* Guarantee 64bit alignment */

	David


  parent reply	other threads:[~2018-07-09 10:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09  4:44 [RESEND PATCH v2] devres: Really align data field to unsigned long long Alexey Brodkin
2018-07-09  4:44 ` Alexey Brodkin
2018-07-09  5:48 ` Greg KH
2018-07-09  5:48   ` Greg KH
2018-07-09  6:46   ` Alexey Brodkin
2018-07-09  6:46     ` Alexey Brodkin
2018-07-09  7:06     ` greg
2018-07-09  7:06       ` greg
2018-07-09  7:17       ` Alexey Brodkin
2018-07-09  7:17         ` Alexey Brodkin
2018-07-09  7:33         ` greg
2018-07-09  7:33           ` greg
2018-07-09  7:07   ` Geert Uytterhoeven
2018-07-09  7:07     ` Geert Uytterhoeven
2018-07-09  7:22     ` Alexey Brodkin
2018-07-09  7:22       ` Alexey Brodkin
2018-07-09  7:52       ` Geert Uytterhoeven
2018-07-09  7:52         ` Geert Uytterhoeven
2018-07-09  8:37         ` Alexey Brodkin
2018-07-09  8:37           ` Alexey Brodkin
2018-07-09  9:03           ` Geert Uytterhoeven
2018-07-09  9:03             ` Geert Uytterhoeven
2018-07-09  9:16 ` David Laight
2018-07-09  9:16   ` David Laight
2018-07-09  9:23   ` Geert Uytterhoeven
2018-07-09  9:23     ` Geert Uytterhoeven
2018-07-09  9:54     ` David Laight
2018-07-09  9:54       ` David Laight
2018-07-09  9:59   ` Alexey Brodkin
2018-07-09  9:59     ` Alexey Brodkin
2018-07-09 10:18     ` David Laight [this message]
2018-07-09 10:18       ` David Laight
2018-07-09 10:23       ` Alexey Brodkin
2018-07-09 10:23         ` Alexey Brodkin
2018-07-09 18:27         ` Vineet Gupta
2018-07-09 18:27           ` Vineet Gupta
2018-07-10  6:42           ` Alexey Brodkin
2018-07-10  6:42             ` Alexey Brodkin

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=91c57eeba2134dd99a9f0e11fa883c7c@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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