Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Todd Dworshak <todd.dworshak@avid.com>,
	'Bruce Cran' <bruce@cran.org.uk>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio 2.1.4 intermittently crashes on windows
Date: Thu, 9 Jan 2014 06:37:09 +0000	[thread overview]
Message-ID: <20140109063709.GA1704@sucs.org> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402954872E64@G4W3202.americas.hpqcorp.net>

On Thu, Jan 09, 2014 at 01:07:56AM +0000, Elliott, Robert (Server Storage) wrote:
> I've seen something similar:
> - 2.1.4 on a Windows Server 2008 R2 system: crash
> 
> This is this error for 2.1.4 on Windows Server 2008 R2: 

<snip>

> (gdb) f 2
> #2  0x0000000000421599 in fio_mutex_up (mutex=0x2f5b10) at mutex.c:151
> 151     mutex.c: No such file or directory.
> (gdb) p mutex
> $1 = (struct fio_mutex *) 0x2f5b10
> (gdb) p *mutex
> $2 = {lock = 0x1bab1f00d, cond = 0x100000000, value = 0, waiters = 0, magic = 172}

This is crazy - the magic value is 172 rather than 1297437765 but the
fio_mutex_up() function is protected by an assert that checks to see if
the mutex's magic number is wrong. Could you can insert something like
the following after line 149:
assert(mutex->magic == FIO_MUTEX_MAGIC);
to prove that the value has not been stomped on before
pthread_cond_signal is run?

-- 
Sitsofe | http://sucs.org/~sits/

  parent reply	other threads:[~2014-01-09  7:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  1:42 fio 2.1.4 intermittently crashes on windows Todd Dworshak
2013-12-28  2:12 ` Bruce Cran
2014-01-08 22:02   ` Todd Dworshak
2014-01-09  1:07     ` Elliott, Robert (Server Storage)
2014-01-09  2:32       ` Todd Dworshak
2014-01-09  6:37       ` Sitsofe Wheeler [this message]
     [not found]         ` <94D0CD8314A33A4D9D801C0FE68B4029548744AD@G4W3202.americas.hpqcorp.net>
2014-01-10  5:21           ` Sitsofe Wheeler
2014-01-10  6:11             ` Bruce Cran
2014-01-10 16:46               ` Elliott, Robert (Server Storage)
2014-01-27 20:46                 ` Sitsofe Wheeler
2014-01-28 21:08                 ` Bruce Cran

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=20140109063709.GA1704@sucs.org \
    --to=sitsofe@yahoo.com \
    --cc=Elliott@hp.com \
    --cc=bruce@cran.org.uk \
    --cc=fio@vger.kernel.org \
    --cc=todd.dworshak@avid.com \
    /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