From: Jan Stancek <jstancek@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] ipc/shmat: pick suitable base_addr before each testcase
Date: Fri, 26 Oct 2012 07:15:30 -0400 (EDT) [thread overview]
Message-ID: <830469677.390108.1351250130900.JavaMail.root@redhat.com> (raw)
In-Reply-To: <a8673441164c2c578dc5a485640a433f3e92c5d3.1351248861.git.jstancek@redhat.com>
----- Original Message -----
> From: "Jan Stancek" <jstancek@redhat.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Friday, 26 October, 2012 12:54:37 PM
> Subject: [LTP] [PATCH] ipc/shmat: pick suitable base_addr before each testcase
>
> This test picked fixed address in setup() which was used throughout
> the test. There has been reports that it can fail with EINVAL.
>
> I could reproduce it by adding single printf in between
> detach/attach:
> http://article.gmane.org/gmane.linux.ltp/16480
>
> This patch picks suitable base_addr before each test. So even if
> glibc
> would mmap extra page with addr == base_addr picked by setup(),
> new suitable address will be chosen.
>
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
I'll send v2, getipckey() appears to return only few unique
keys and after couple loops this fails because it returns key
which already exists.
Regards,
Jan
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-10-26 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 10:54 [LTP] [PATCH] ipc/shmat: pick suitable base_addr before each testcase Jan Stancek
2012-10-26 11:15 ` 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=830469677.390108.1351250130900.JavaMail.root@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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