public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fix padding computation in struct ucontext
Date: Wed, 27 Feb 2013 11:53:54 +0000	[thread overview]
Message-ID: <20130227115354.GB2293@MacBook-Pro.local> (raw)
In-Reply-To: <mvmy5ebt3ol.fsf@hawking.suse.de>

On Tue, Feb 26, 2013 at 04:55:54PM +0000, Andreas Schwab wrote:
> The expression to compute the padding needed to fill the uc_sigmask field
> to 1024 bits actually computes the padding needed for 1080 bits.
> Fortunately, due to the 16-byte alignment of the following field
> (uc_mcontext) the definition in glibc contains enough bytes of padding
> after uc_sigmask so that the overall offsets and size match in both
> definitions.
> 
> Signed-off-by: Andreas Schwab <schwab@suse.de>

It looks like I messed the bits vs bytes. Luckily we have the 16-byte
alignment of the last element in ucontext. I'll send the patch upstream.

Thanks.

-- 
Catalin

      reply	other threads:[~2013-02-27 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 16:55 [PATCH] arm64: fix padding computation in struct ucontext Andreas Schwab
2013-02-27 11:53 ` Catalin Marinas [this message]

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=20130227115354.GB2293@MacBook-Pro.local \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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