From: Jens Axboe <axboe@kernel.dk>
To: "Roopeshakumar Narayansa Shalgar (rshalgar)" <rshalgar@cisco.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Fio crashes in setup_file
Date: Wed, 22 Jan 2014 14:21:08 -0800 [thread overview]
Message-ID: <20140122222108.GX20347@kernel.dk> (raw)
In-Reply-To: <F9567754259D974D88F5F5337C9D21962022C70F@xmb-aln-x11.cisco.com>
On Mon, Jan 20 2014, Roopeshakumar Narayansa Shalgar (rshalgar) wrote:
> Hi,
>
> The moment I define a new variable under thread_options I start seeing
> a crash in 'setup_files' files Function. Backtrace points to the
> following lline:
>
> if (td->io_ops->setup). Gdb shows the value of null for io_ops.
>
>
> So essentially what's happenings is io_ops is not getting set
> correctly when I add a new variable under 'thread_options' structures.
>
>
> This can be easily reproduced by simply adding a variable under
> thread_options structiure. No other changes are required. Can someone
> help?
Might be a build issue, try to do a make clean after modifying the
header.
--
Jens Axboe
prev parent reply other threads:[~2014-01-22 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 10:51 Fio crashes in setup_file Roopeshakumar Narayansa Shalgar (rshalgar)
2014-01-22 22:21 ` Jens Axboe [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=20140122222108.GX20347@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=rshalgar@cisco.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