From: Al Viro <viro@ZenIV.linux.org.uk>
To: Christopher Li <sparse@chrisli.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>, linux-sparse@vger.kernel.org
Subject: Re: more "unreplaced symbol" warnings
Date: Tue, 31 May 2011 19:30:30 +0100 [thread overview]
Message-ID: <20110531183030.GM11521@ZenIV.linux.org.uk> (raw)
In-Reply-To: <BANLkTi=_0Xe8Fuq9aJ69Zqx3iQYq6E9N5w@mail.gmail.com>
On Tue, May 31, 2011 at 10:39:52AM -0700, Christopher Li wrote:
> On Sun, May 29, 2011 at 2:54 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > I see that there was a short thread in Feb. 2008 about unreplaced symbols.
> > Here are more warnings from Linux 2.6.39-git18 mainline.
> > Obviously lots of them are just repeats, but this is what I get from x86_64
> > allmodconfig.
> >
> > Any suggestions about how to eliminate them?
> > Thanks.
> >
> > include/linux/swab.h:51:16: warning: unreplaced symbol 'val'
> > include/linux/swab.h:51:16: warning: unreplaced symbol 'val'
>
> I am trying to produce those now. If you know which C file causing
> this warning would be great.
>
> It just hit me that, if there is a script to help reproduce the error
> would be great. I just give this error line it emits. The script takes the
> C source file and try to eliminate as much lines as possible while
> still reproduce the error.
Hell knows... net/bridge/br_netfilter.c will give you just that. From the
look of other similar instances, I suspect that it's handling of case ...:
somewhere:
static inline unsigned int nf_bridge_encap_header_len(const struct sk_buff *skb)
{
switch (skb->protocol) {
case __cpu_to_be16(ETH_P_8021Q):
return VLAN_HLEN;
case __cpu_to_be16(ETH_P_PPP_SES):
return PPPOE_SES_HLEN;
default:
return 0;
}
}
also warns the same way on both __cpu_to_be16()...
next prev parent reply other threads:[~2011-05-31 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 21:54 more "unreplaced symbol" warnings Randy Dunlap
2011-05-31 17:39 ` Christopher Li
2011-05-31 18:30 ` Al Viro [this message]
2011-05-31 18:58 ` Al Viro
2011-05-31 19:05 ` Christopher Li
2011-06-01 7:41 ` Christopher Li
2011-08-15 19:34 ` Christopher Li
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=20110531183030.GM11521@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sparse@chrisli.org \
/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;
as well as URLs for NNTP newsgroup(s).