From owner-freebsd-bugs@FreeBSD.ORG  Tue Sep 23 16:16:50 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 02FD2603
 for <freebsd-bugs@FreeBSD.org>; Tue, 23 Sep 2014 16:16:50 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id DD94F392
 for <freebsd-bugs@FreeBSD.org>; Tue, 23 Sep 2014 16:16:49 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8NGGnoI040795
 for <freebsd-bugs@FreeBSD.org>; Tue, 23 Sep 2014 16:16:49 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 193649] ring->nr_buf_size will be calculated wrongly on PPC
 machine
Date: Tue, 23 Sep 2014 16:16:50 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: thomasyang1206@126.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-193649-8-oS9retnjoc@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193649-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-193649-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 16:16:50 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193649

--- Comment #1 from dongshan <thomasyang1206@126.com> ---
the bug is caused as following:
imaging a 32-bit integer 0x00000800, on little endian machine, the data in
memory is arranged like this:

[0000 0000]        0000
[0000 0001]        0000
[0000 0002]        1000
[0000 0003]        0000
[0000 0004]        0000
[0000 0005]        0000
[0000 0006]        0000
[0000 0007]        0000
However, on a big endian machine, the value in memory is:
[0000 0000]        0000      
[0000 0001]        0000
[0000 0002]        0000
[0000 0003]        0000
[0000 0004]        0000
[0000 0005]        1000
[0000 0006]        0000
[0000 0007]        0000
-------------------------------------------------------------------------------
Here is the trick:
    uint32_t foo; // let assume the address of foo is 0x0, as showed above.
    uint32_t *p = &foo;
    *(uint16_t *)p = 0x00000800;
    printf("foo: 0x%x", foo); // the output of foo will be 0x08000000
        printf("foo1:0x%x", (uint16_t)foo); // the output will be 0x00000800
Dump the memory on big endian machine:
[0000 0000]        0000      
[0000 0001]        1000
[0000 0002]        0000
[0000 0003]        0000
[0000 0004]        0000
[0000 0005]        0000
[0000 0006]        0000
[0000 0007]        0000

-- 
You are receiving this mail because:
You are the assignee for the bug.