Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Sébastien Bouchex Bellomié" <sbouchex@infovista.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Solaris issue with packed stat structures
Date: Thu, 30 Oct 2014 08:42:46 -0600	[thread overview]
Message-ID: <54524E66.50502@kernel.dk> (raw)
In-Reply-To: <14c6d46030d24183a714b5cf90ca81cc@DB4PR03MB572.eurprd03.prod.outlook.com>

On 2014-10-30 08:34, S�bastien Bouchex Bellomi� wrote:
> Hi,
>
> I'm the latest source on solaris SPARC and I have BUS errors when generating stats :
>
> Stack looks like this :
>
> 0002bac4 sum_stat (17973e, fbc05b38, 1, 0, 0, 22) + 38
>   0002cf24 sum_thread_stats (179526, fbc05920, 1, 0, fbd7de7c, 4) + a8
>   0003113c __show_run_stats (fe40ad88, 400, 0, 0, 0, 0) + 1124
>   000b0b10 fio_backend (0, ffbffcf4, 0, 0, 0, 15c174) + 200
>   000e6a40 main     (2, ffbffcf4, ffbffd00, 166130, 0, fefe0180) + c4
>   00017844 _start   (0, 0, 0, 0, 0, 0) + 5c
>
> It works fine on intel processors because the hardware is handling the misalignment but on Sparc, it is not handled, so a BUS error is generated
>
> To fix this issue, I have added some padding here :
>
> [...]
> uint16_t continue_on_error;
> uint16_t continue_on_error_pad;				// <<<<<==== Pading here
> uint64_t total_err_count;
> uint32_t first_error;

What -git revision are you on? The latest should have the correct padding.

-- 
Jens Axboe



  reply	other threads:[~2014-10-30 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 14:34 Solaris issue with packed stat structures Sébastien Bouchex Bellomié
2014-10-30 14:42 ` Jens Axboe [this message]
2014-10-30 14:55   ` Sébastien Bouchex Bellomié
2014-10-30 14:56     ` Jens Axboe
2014-10-30 17:12       ` Sébastien Bouchex Bellomié

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=54524E66.50502@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=sbouchex@infovista.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