public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Anatoly Pugachev <matorola@gmail.com>,
	linux-ext4@vger.kernel.org,
	debian-sparc <debian-sparc@lists.debian.org>
Subject: Re: [sparc64] sigbus in e2fsck
Date: Tue, 30 Aug 2016 18:45:45 +0200	[thread overview]
Message-ID: <87shtmnr2e.fsf@oracle.com> (raw)
In-Reply-To: <20160830145810.rgms25xlnatnyxir@thunk.org> (Theodore Ts'o's message of "Tue, 30 Aug 2016 10:58:10 -0400")

    
    typedef struct journal_revoke_header_s
    {
    	journal_header_t r_header;
    	int		 r_count;	/* Count of bytes used in the block */
    } journal_revoke_header_t;
    
    The "int" above should be a __u32.  What is the size of int on
    sparc64?  Is it by any chance 8 bytes?  If that's the problem then I'm
    kind of surprised we haven't run into massive problems earlier, as
    this looks like a long standing bug.

sizeof(int) == 4 in both sparc64-linux-gnu and sparcv9-linux-gnu (32bit)
targets.

      parent reply	other threads:[~2016-08-30 16:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 12:42 [sparc64] sigbus in e2fsck Anatoly Pugachev
2016-08-30 12:56 ` John Paul Adrian Glaubitz
2016-08-30 14:58   ` Theodore Ts'o
2016-08-30 15:03     ` John Paul Adrian Glaubitz
2016-08-30 15:12     ` Anatoly Pugachev
2016-08-30 19:16       ` Theodore Ts'o
2016-08-30 20:17         ` Anatoly Pugachev
2016-08-30 20:25           ` Darrick J. Wong
2016-09-01  1:26             ` Theodore Ts'o
2016-08-30 16:45     ` Jose E. Marchesi [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=87shtmnr2e.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=debian-sparc@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=matorola@gmail.com \
    --cc=tytso@mit.edu \
    /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