Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org,
	linux-arch@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	stable@vger.kernel.org
Subject: Re: [RESEND PATCH v2] devres: Really align data field to unsigned long long
Date: Mon, 9 Jul 2018 07:48:42 +0200	[thread overview]
Message-ID: <20180709054842.GB7618@kroah.com> (raw)
In-Reply-To: <20180709044444.6397-1-abrodkin@synopsys.com>

On Mon, Jul 09, 2018 at 07:44:44AM +0300, Alexey Brodkin wrote:
> 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.

So is this something you hit today?  If not, why is this needed for
stable kernels?

> That's because even on CPUs capable of non-aligned data access LL/SC
> instructions require strict alignment.

Are you going to hit this code with all types of structures?  What
happens when you do have an unaligned access?

> 
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

You didn't cc: this address :(

> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: stable@vger.kernel.org
> ---
> 
> Changes v1 -> v2:
> 
>  * Reworded commit message
>  * Inserted comment right in source [Thomas]
> 
>  drivers/base/devres.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/base/devres.c b/drivers/base/devres.c
> index f98a097e73f2..466fa59c866a 100644
> --- a/drivers/base/devres.c
> +++ b/drivers/base/devres.c
> @@ -24,8 +24,12 @@ struct devres_node {
>  
>  struct devres {
>  	struct devres_node		node;
> -	/* -- 3 pointers */
> -	unsigned long long		data[];	/* guarantee ull alignment */
> +	/*
> +	 * 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.
> +	 */
> +	unsigned long long		data[] __aligned(sizeof(unsigned long long));
>  };

Does this change the padding today for any other arches?  If so, does
the increased memory usage cause any noticable issues?

thanks,

greg k-h

  parent reply	other threads:[~2018-07-09  5:48 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 [this message]
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
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=20180709054842.GB7618@kroah.com \
    --to=greg@kroah.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --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