public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] mtest06 failures
Date: Tue, 7 Apr 2015 15:15:57 +0200	[thread overview]
Message-ID: <20150407131556.GA9535@rei> (raw)
In-Reply-To: <1301134399.9357345.1428055489965.JavaMail.zimbra@redhat.com>

Hi!
> <<<test_start>>>
> tag=mtest06 stime=1427900338
> cmdline="  mmap1 -x 0.05"
> contacts=""
> analysis=exit
> <<<test_output>>>
> mmap1       0  TINFO  :  created writing thread[70366651085264]
> mmap1       0  TINFO  :  [70366651085264] - map, change contents, unmap files 1000 times
> mmap1       0  TINFO  :  created reading thread[70366642696656]
> mmap1       0  TINFO  :  [70366642696656] - read contents of memory (nil) 1000 times
> mmap1       1  TFAIL  :  mmap1.c:400: thread [70366642696656] - process exited with -1
> <<<execution_status>>>
> initiation_status="ok"
> duration=1 termination_type=exited termination_id=1 corefile=no
> cutime=23 cstime=46
> <<<test_end>>>
> 
> ret code -1 indicates, that it hit:
>     if (map_address[j] != 'a')
>         pthread_exit((void *)-1);
> 
> I think what happens is that map_write_unmap() unmaps the memory,
> and something else mmaps into the same location. gdb breakpoints on
> mmap found couple places which could be responsible, pthread_exit()
> was one of them.
> 
> 2 ideas came to mind:
> 1. clear map_address after munmap
>    This however seems to go against what the testcase is trying to do
> 2. make sure mmap for map_address happens in place which is less likely
>    to be used in future mmaps

I do not recall mtest06 failing this way, but it's quite possible that
something from libc will trigger mmap() to allocate memory.

The patch looks good to me.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2015-04-07 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <214042481.9356038.1428054865150.JavaMail.zimbra@redhat.com>
2015-04-03 10:04 ` [LTP] mtest06 failures Jan Stancek
2015-04-07 13:15   ` Cyril Hrubis [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=20150407131556.GA9535@rei \
    --to=chrubis@suse.cz \
    --cc=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