Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Geert Uytterhoeven' <geert@linux-m68k.org>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	arcml <linux-snps-arc@lists.infradead.org>,
	Linux-Arch <linux-arch@vger.kernel.org>, Greg KH <greg@kroah.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	stable <stable@vger.kernel.org>
Subject: RE: [RESEND PATCH v2] devres: Really align data field to unsigned long long
Date: Mon, 9 Jul 2018 09:54:54 +0000	[thread overview]
Message-ID: <3e34f94963ff442ca09cef84fdf160fd@AcuMS.aculab.com> (raw)
In-Reply-To: <CAMuHMdUdTNpt6G1gzdd6tg9cTo4+kOQCP0Ekouhogug_1sJNPg@mail.gmail.com>

From: Geert Uytterhoeven
> Sent: 09 July 2018 10:23
> On Mon, Jul 9, 2018 at 11:15 AM David Laight <David.Laight@aculab.com> wrote:
> > From: Alexey Brodkin
> > > Sent: 09 July 2018 05:45
> > > Depending on ABI "long long" type of a particular 32-bit CPU
> > > might be aligned by either word (32-bits) or double word (64-bits).
> > > Make sure "data" is really 64-bit aligned for any 32-bit CPU.
> > >
> > > At least for 32-bit ARC cores ABI requires "long long" types
> > > to be aligned by normal 32-bit word. This makes "data" field aligned to
> > > 12 bytes. Which is still OK as long as we use 32-bit data only.
> > >
> > > But once we want to use native atomic64_t type (i.e. when we use special
> > > instructions LLOCKD/SCONDD for accessing 64-bit data) we easily hit
> > > misaligned access exception.
> >
> > Shouldn't there be a typedef for the actual type.
> > Perhaps it is even atomic64_t ?
> > And have the __aligned(8) applied to that typedef ??
> 
> That indeed sounds like the best thing to do, as it will fix this issue in other
> places, too.

Something like:
typedef struct {
	u64 val __aligned(8);
} atomic64_t;

would pick up most errors.
Including all the places that fail to use atomic_read().

	David


  reply	other threads:[~2018-07-09  9:54 UTC|newest]

Thread overview: 19+ 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  5:48 ` Greg KH
2018-07-09  6:46   ` Alexey Brodkin
2018-07-09  7:06     ` greg
2018-07-09  7:17       ` Alexey Brodkin
2018-07-09  7:33         ` greg
2018-07-09  7:07   ` Geert Uytterhoeven
2018-07-09  7:22     ` Alexey Brodkin
2018-07-09  7:52       ` Geert Uytterhoeven
2018-07-09  8:37         ` Alexey Brodkin
2018-07-09  9:03           ` Geert Uytterhoeven
2018-07-09  9:16 ` David Laight
2018-07-09  9:23   ` Geert Uytterhoeven
2018-07-09  9:54     ` David Laight [this message]
2018-07-09  9:59   ` Alexey Brodkin
2018-07-09 10:18     ` David Laight
2018-07-09 10:23       ` Alexey Brodkin
2018-07-09 18:27         ` Vineet Gupta
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=3e34f94963ff442ca09cef84fdf160fd@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=geert@linux-m68k.org \
    --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