From: Keir Fraser <keir@xensource.com>
To: Jacek Konieczny <jajcus@jajcus.net>, xen-devel@lists.xensource.com
Subject: Re: netfront: rx->offset: 12, size: 4294967295
Date: Mon, 04 Jun 2007 13:52:30 +0100 [thread overview]
Message-ID: <C289C99E.FF11%keir@xensource.com> (raw)
In-Reply-To: <20070604124040.GC2158@jajo.eggsoft.pl>
On 4/6/07 13:40, "Jacek Konieczny" <jajcus@jajcus.net> wrote:
> Ok, got it. It seems like a bug (feature?) of my compiler (gcc 4.2.0 and
> several earlier snapshots of gcc 4.2) or maybe some race condition (is
> it possible? anything else writes the netif structure?)
>
> The problem occurs in line 377 of drivers/xen/netback/xenbus.c:
>
> be->netif->copying_receiver = !!rx_copy;
My suspicion is that, strictly speaking, the assignment of 1 to
copying_receiver is invalid because a single-bit bitfield can only hold the
values -1 and 0. Older gcc perhaps mapped 1 to -1, but 4.2.0 is mapping 1 to
0 (or choosing to do that as an optimisation, since it has the choice, and
hence can simplify the code to always write zero in this case). That sucks.
Can you try changing the definition of copying_receiver in netback/common.h
to be 'unsigned copying_receiver:1' instead of int:1?
-- Keir
next prev parent reply other threads:[~2007-06-04 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 14:05 netfront: rx->offset: 12, size: 4294967295 Jacek Konieczny
2007-06-01 14:22 ` Keir Fraser
2007-06-01 16:56 ` Jacek Konieczny
2007-06-01 17:11 ` Jacek Konieczny
2007-06-01 17:38 ` Keir Fraser
2007-06-01 19:01 ` Jacek Konieczny
2007-06-02 10:13 ` Keir Fraser
2007-06-02 18:49 ` Jacek Konieczny
2007-06-03 8:33 ` Keir Fraser
2007-06-03 11:51 ` Jacek Konieczny
2007-06-04 12:40 ` Jacek Konieczny
2007-06-04 12:52 ` Keir Fraser [this message]
2007-06-04 14:05 ` Jacek Konieczny
2007-06-04 14:08 ` Keir Fraser
2007-06-06 0:30 ` Mark Williamson
2007-06-05 21:48 ` Herbert Xu
2007-06-05 21:57 ` Mark Williamson
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=C289C99E.FF11%keir@xensource.com \
--to=keir@xensource.com \
--cc=jajcus@jajcus.net \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.