From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] [COMMITTED] syscalls/shmat01: Fix test on 32bit
Date: Tue, 12 Sep 2017 11:24:31 -0400 (EDT) [thread overview]
Message-ID: <1458338308.13858491.1505229871475.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170912151827.20551-1-chrubis@suse.cz>
----- Original Message -----
> The problem there is that the address casted to intptr_t yields negative
> number which when divided then multiplied by SHMLBA aligns the value up
> instead of down.
>
> The fix is simple, we cast the pointer to uintptr_t instead of intptr_t
> and also include stdint.h explicitly.
>
> Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
You have beat me by ~3 minutes. I was just going to push,
did final 'git pull --rebase' and my commit disappeared :-).
Regards,
Jan
prev parent reply other threads:[~2017-09-12 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 15:18 [LTP] [PATCH 1/2] [COMMITTED] syscalls/shmat01: Fix test on 32bit Cyril Hrubis
2017-09-12 15:18 ` [LTP] [PATCH 2/2] [COMMITTED] syscalls/shmat: Print expected and actual address on failure Cyril Hrubis
2017-09-12 15:24 ` Jan Stancek [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=1458338308.13858491.1505229871475.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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