Skip to contentSkip to conversation

compilation warnings

2.6.29-rc2-git2 Rufus & Azrael 5 participants 11 messages Jan 27, 2009

lore
Share & tools
lore
#0 lore raw

Hi all,

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Quoted 462 lines

sound/pci/hda/hda_codec.c: In function ‘get_empty_pcm_device’:
sound/pci/hda/hda_codec.c:2544: attention : ‘dev’ may be used uninitialized in this function

drivers/i2c/i2c-core.c: In function ‘i2c_new_device’:
drivers/i2c/i2c-core.c:283: attention : ‘i2c_attach_client’ is deprecated (declared at include/linux/i2c.h:434) drivers/i2c/i2c-core.c: In function ‘i2c_del_adapter’:
drivers/i2c/i2c-core.c:646: attention : ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154) drivers/i2c/i2c-core.c: In function ‘i2c_register_driver’:
drivers/i2c/i2c-core.c:713: attention : ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154) drivers/i2c/i2c-core.c: In function ‘__detach_adapter’:
drivers/i2c/i2c-core.c:780: attention : ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154) drivers/i2c/i2c-core.c: Hors de toute fonction :
drivers/i2c/i2c-core.c:876: attention : ‘i2c_attach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:827) drivers/i2c/i2c-core.c:876: attention : ‘i2c_attach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:827) drivers/i2c/i2c-core.c:904: attention : ‘i2c_detach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:879) drivers/i2c/i2c-core.c:904: attention : ‘i2c_detach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:879)

drivers/media/video/v4l2-common.c: In function ‘v4l2_i2c_attach’:
drivers/media/video/v4l2-common.c:875: attention : ‘i2c_attach_client’ is deprecated (declared at include/linux/i2c.h:434)

drivers/uwb/i1480/i1480-est.c:94: attention : ‘i1480_est_id_table’ defined but not used

drivers/uwb/wlp/messages.c: In function ‘wlp_parse_f0’:
drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[15]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[14]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[13]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[12]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[11]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[10]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[9]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[8]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[7]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[6]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[5]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[4]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[3]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘enonce.data[2]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[15]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[14]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[13]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[12]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[11]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[10]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[9]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[8]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[7]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[6]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[5]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[4]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[3]’ may be used uninitialized in this function drivers/uwb/wlp/messages.c:906: attention : ‘rnonce.data[2]’ may be used uninitialized in this function

drivers/uwb/whc-rc.c:451: attention : ‘whcrc_id_table’ defined but not used

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/mtd/inftl-user.h:61: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/mtd/jffs2-user.h:20: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm-generic/fcntl.h:127: leaks CONFIG_64BIT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm-generic/fcntl.h:149: leaks CONFIG_64BIT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/can/bcm.h:29: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/audio.h:133: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/dmx.h:27: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/dmx.h:90: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/video/edid.h:4: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/sound/hdsp.h:33: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/video/sisfb.h:25: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/video/sisfb.h:78: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/video/uvesafb.h:5: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/frontend.h:29: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/frontend.h:76: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/net.h:27: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/net.h:31: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/video.h:29: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dvb/video.h:102: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/netfilter/xt_conntrack.h:40: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nfsd/export.h:13: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nfsd/nfsfh.h:17: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nfsd/nfsfh.h:28: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nfsd/stats.h:32: leaks CONFIG_NFSD to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nfsd/syscall.h:12: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/raid/md_p.h:85: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nfsd/syscall.h:104: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/spi/spidev.h:83: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/tc_act/tc_gact.h:19: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/tc_act/tc_mirred.h:16: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/tc_act/tc_pedit.h:19: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/tc_ematch/tc_em_cmp.h:8: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/tc_ematch/tc_em_meta.h:18: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/tc_ematch/tc_em_nbyte.h:8: found __[us]{8,16,32,64} type without #include <linux/types.h> /var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/tc_ematch/tc_em_text.h:11: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/usb/cdc.h:50: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/acct.h:62: leaks CONFIG_M68K to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/aio_abi.h:58: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/atalk.h:15: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/atmbr2684.h:88: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/usb/gadgetfs.h:21: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/atmdev.h:103: leaks CONFIG_COMPAT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/auto_fs4.h:132: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/bfs_fs.h:24: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/blktrace_api.h:96: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/capability.h:72: leaks CONFIG_SECURITY to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/capability.h:73: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/cdrom.h:155: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/cgroupstats.h:31: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/cm4000_cs.h:22: leaks CONFIG_COMPAT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/coda_psdev.h:90: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dlm_plock.h:25: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/dn.h:75: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/edd.h:70: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/efs_fs_sb.h:49: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/elf-fdpic.h:61: leaks CONFIG_MMU to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/elf-fdpic.h:62: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/elf.h:379: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/elf.h:387: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/elf.h:401: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/elf.h:402: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/elfcore.h:59: leaks CONFIG_BINFMT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/errqueue.h:6: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/fb.h:381: leaks CONFIG_FB to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/flat.h:16: leaks CONFIG_BINFMT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/genetlink.h:12: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/gfs2_ondisk.h:109: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/hid.h:66: leaks CONFIG_HID to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/hid.h:69: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/hid.h:76: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/hiddev.h:40: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/icmpv6.h:8: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_addr.h:8: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_addrlabel.h:15: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_fc.h:37: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_hippi.h:82: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_link.h:9: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_ppp.h:96: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_strip.h:22: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/if_tr.h:37: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/igmp.h:31: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/in6.h:47: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/in6.h:49: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/inet_diag.h:16: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/ip6_tunnel.h:21: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/ipv6.h:26: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/ipv6_route.h:42: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/ipx.h:13: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/irda.h:127: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kernel.h:39: leaks CONFIG_NUMA to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kernel.h:40: leaks CONFIG_NUMA to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kernel.h:46: leaks CONFIG_FTRACE to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kernel.h:47: leaks CONFIG_FTRACE to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kvm.h:61: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kvm.h:64: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kvm.h:387: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kvm.h:391: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/kvm.h:396: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/minix_fs.h:34: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/msdos_fs.h:100: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/neighbour.h:8: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nfs_idmap.h:55: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nubus.h:232: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nubus.h:296: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nubus.h:298: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/nubus.h:302: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/phonet.h:50: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/pkt_cls.h:122: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/pkt_cls.h:306: leaks CONFIG_NET to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/pkt_cls.h:307: leaks CONFIG_NET to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/pkt_sched.h:32: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/pktcdvd.h:36: leaks CONFIG_CDROM to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/ppp_defs.h:50: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/random.h:39: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/raw.h:16: leaks CONFIG_MAX to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:64: leaks CONFIG_REISERFS to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:81: leaks CONFIG_REISERFS to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:687: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:995: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:997: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1467: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1587: leaks CONFIG_QUOTA to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1760: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1764: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1766: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1769: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1771: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1805: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1908: leaks CONFIG_PROC to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1948: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1949: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1950: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1951: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1962: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1963: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/reiserfs_fs.h:1964: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/rtnetlink.h:328: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/signalfd.h:19: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/socket.h:27: leaks CONFIG_PROC to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/socket.h:29: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/socket.h:262: leaks CONFIG_COMPAT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:33: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:34: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:35: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:36: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:37: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:39: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:40: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:41: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/sound.h:42: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1047: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1048: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1049: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1050: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1051: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1053: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1055: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1056: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1061: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1062: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1078: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/soundcard.h:1079: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/synclink.h:209: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/taskstats.h:44: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/types.h:114: leaks CONFIG_LBD to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/video_decoder.h:7: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/video_encoder.h:5: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/videodev.h:18: leaks CONFIG_VIDEO to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/videodev.h:53: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/videodev.h:313: leaks CONFIG_VIDEO to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/videodev2.h:1477: leaks CONFIG_VIDEO to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/virtio_blk.h:21: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/virtio_console.h:15: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/linux/virtio_net.h:28: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/boot.h:14: leaks CONFIG_PHYSICAL to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/boot.h:15: leaks CONFIG_PHYSICAL to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/boot.h:16: leaks CONFIG_PHYSICAL to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/boot.h:18: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/e820.h:13: leaks CONFIG_NODES to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/e820.h:27: leaks CONFIG_EFI to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/e820.h:44: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/kvm.h:9: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/kvm.h:16: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/mce.h:7: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/mce.h:29: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/mtrr.h:61: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/prctl.h:9: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/prctl.h:10: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/prctl.h:11: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/ptrace-abi.h:83: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/ptrace-abi.h:86: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/ptrace-abi.h:93: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/ptrace-abi.h:143: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:15: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:16: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:17: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:23: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:24: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:51: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:52: extern's make no sense in userspace

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/setup.h:54: leaks CONFIG_PARAVIRT to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/sigcontext.h:5: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/sigcontext.h:24: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/sigcontext32.h:20: found __[us]{8,16,32,64} type without #include <linux/types.h>

Quoted 7 lines

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/swab.h:4: include of <linux/types.h> is preferred over <asm/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/swab.h:7: found __[us]{8,16,32,64} type without #include <linux/types.h>

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/swab.h:10: leaks CONFIG_X86 to userspace where it is not valid

/var/tmp/kernel/linux-2.6.29-rc2/usr/include/asm/swab.h:40: leaks CONFIG_X86 to userspace where it is not valid

I found this patches series in LKML for some of these warnings :
http://lkml.org/lkml/2008/11/28/206

but they seem not ready to be pulled in mainline.

Regards.

#1 lore raw

At Tue, 27 Jan 2009 08:15:29 +0100,

Quoted 6 lines · Rufus & Azrael

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Quoted 3 lines

sound/pci/hda/hda_codec.c: In function ‘get_empty_pcm_device’:
sound/pci/hda/hda_codec.c:2544: attention : ‘dev’ may be used uninitialized in this function

A bogus warning. Ignore this.

thanks,

Takashi

#2 lore raw
Quoted 10 lines · Takashi Iwai

At Tue, 27 Jan 2009 08:15:29 +0100,

Quoted 6 lines · Rufus & Azrael

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Quoted 3 lines

sound/pci/hda/hda_codec.c: In function ‘get_empty_pcm_device’:
sound/pci/hda/hda_codec.c:2544: attention : ‘dev’ may be used uninitialized in this function

A bogus warning. Ignore this.

No matter how bogus it is, it should be fixed. Otherwise this is wasting the time of users and developers over and over again.

Signature · 1 line
Jean Delvare
#3 lore raw

At Tue, 27 Jan 2009 09:46:28 +0100,

Quoted 7 lines · Jean Delvare
Quoted 5 lines · Takashi Iwai

At Tue, 27 Jan 2009 08:15:29 +0100,

Quoted 3 lines · Rufus & Azrael

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Quoted 3 lines

sound/pci/hda/hda_codec.c: In function ‘get_empty_pcm_device’:
sound/pci/hda/hda_codec.c:2544: attention : ‘dev’ may be used uninitialized in this function

A bogus warning. Ignore this.

No matter how bogus it is, it should be fixed. Otherwise this is wasting the time of users and developers over and over again.

Well, it's a bug of gcc appearing only in a certain version, so most people won't see it.

Of course, we can put uninitialized_var(). But, I don't basically like adding it unconditionally...

Takashi

#4 lore raw
Quoted 15 lines · Takashi Iwai

At Tue, 27 Jan 2009 09:46:28 +0100,

Quoted 13 lines · Jean Delvare
Quoted 10 lines · Takashi Iwai

At Tue, 27 Jan 2009 08:15:29 +0100,

Quoted 6 lines · Rufus & Azrael

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Quoted 3 lines

sound/pci/hda/hda_codec.c: In function ‘get_empty_pcm_device’:
sound/pci/hda/hda_codec.c:2544: attention : ‘dev’ may be used uninitialized in this function

A bogus warning. Ignore this.

Quoted 8 lines
Quoted 2 lines

No matter how bogus it is, it should be fixed. Otherwise this is wasting the time of users and developers over and over again.

Well, it's a bug of gcc appearing only in a certain version, so most people won't see it.

Of course, we can put uninitialized_var(). But, I don't basically like adding it unconditionally...

People will again and again look at this warning and waste time deciding that "it's a bogus warning" or even report it. As time goes on does the human cost get larger, linearly.

Furthermore, if everyone in the kernel behaves like that we'll literally have dozens (even hundreds) of build warnings that might be bogus but which also obscure other, real warnings by their sheer mass.

The cost of you adding a oneliner annotation is miniscule compared to that and it is a one-time effort. We already spent more energy on discussing this than it would have taken you to annotate it. Please.

Ingo

#5 lore raw

At Tue, 27 Jan 2009 12:16:31 +0100,

Quoted 28 lines · Ingo Molnar
Quoted 15 lines · Takashi Iwai

At Tue, 27 Jan 2009 09:46:28 +0100,

Quoted 13 lines · Jean Delvare
Quoted 10 lines · Takashi Iwai

At Tue, 27 Jan 2009 08:15:29 +0100,

Quoted 6 lines · Rufus & Azrael

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Quoted 3 lines

sound/pci/hda/hda_codec.c: In function ‘get_empty_pcm_device’:
sound/pci/hda/hda_codec.c:2544: attention : ‘dev’ may be used uninitialized in this function

A bogus warning. Ignore this.

Quoted 8 lines
Quoted 2 lines

No matter how bogus it is, it should be fixed. Otherwise this is wasting the time of users and developers over and over again.

Well, it's a bug of gcc appearing only in a certain version, so most people won't see it.

Of course, we can put uninitialized_var(). But, I don't basically like adding it unconditionally...

Quoted 7 lines

People will again and again look at this warning and waste time deciding that "it's a bogus warning" or even report it. As time goes on does the human cost get larger, linearly.

Furthermore, if everyone in the kernel behaves like that we'll literally have dozens (even hundreds) of build warnings that might be bogus but which also obscure other, real warnings by their sheer mass.

The question is rather how often it's really seen.
I've tested 4 different gcc versions and a couple of other versions with cross compiling occasionally, and this warning doesn't appear on any versions.

Quoted 3 lines

The cost of you adding a oneliner annotation is miniscule compared to that and it is a one-time effort. We already spent more energy on discussing this than it would have taken you to annotate it. Please.

Well, did we get a consensus about this? If yes, I'll follow it, of course.

Adding uninitialized_var() essentially means to disable the check, thus a new real bug in future might be overlooked. This is a bigger drawback if it's just a warning that appears in only one old buggy gcc version.

That's why I wrote "adding it *unconditionally*". If the warning appears in many gcc versions, it's worth to hide.

thanks,

Takashi

#6 lore raw
In reply to Takashi Iwai

Hi Takashi,

Quoted 4 lines · Takashi Iwai

At Tue, 27 Jan 2009 09:46:28 +0100,

Quoted 3 lines · Takashi Iwai
Quoted 1 line

A bogus warning. Ignore this.

Quoted 8 lines
Quoted 2 lines

No matter how bogus it is, it should be fixed. Otherwise this is wasting the time of users and developers over and over again.

Well, it's a bug of gcc appearing only in a certain version, so most people won't see it.

Of course, we can put uninitialized_var(). But, I don't basically like adding it unconditionally...

I didn't know about uninitialized_var(), thanks for the hint.

My experience with these warnings is that, in many cases, it is possible to write the code differently so that it is clear to the compiler that the variable is never used uninitialized. In some cases, doing so also makes the code easier to read for humans and less likely to break in the future.

Of course, in some cases the problem is simply that the compiler is too stupid to understand even simple things, but in other cases these warnings might be a good opportunity to rewrite the code in a way that is easier to understand.

Signature · 1 line
Jean Delvare
#7 lore raw
Quoted 24 lines · Jean Delvare

Hi Takashi,

Quoted 4 lines · Takashi Iwai

At Tue, 27 Jan 2009 09:46:28 +0100,

Quoted 3 lines · Takashi Iwai
Quoted 1 line

A bogus warning. Ignore this.

Quoted 8 lines
Quoted 2 lines

No matter how bogus it is, it should be fixed. Otherwise this is wasting the time of users and developers over and over again.

Well, it's a bug of gcc appearing only in a certain version, so most people won't see it.

Of course, we can put uninitialized_var(). But, I don't basically like adding it unconditionally...

I didn't know about uninitialized_var(), thanks for the hint.

My experience with these warnings is that, in many cases, it is possible to write the code differently so that it is clear to the compiler that the variable is never used uninitialized. In some cases, doing so also makes the code easier to read for humans and less likely to break in the future.

Quoted 4 lines

Of course, in some cases the problem is simply that the compiler is too stupid to understand even simple things, but in other cases these warnings might be a good opportunity to rewrite the code in a way that is easier to understand.

And even in the cases where the compiler is stupid, leaving a warning around:

1) Does not get compiler bugs fixed any faster [only true competition between compilers gets compiler bugs fixed any faster]

2) Has ongoing and irreversible maintenance costs for _all of us in the kernel_

3) for every bogus compiler warning there's a dozen warnings where the compiler told us that _we_ were doing something stupid. All things considered the false positive ratio is still a fair deal.

So leaving them around is a bit like making a political point by burning yourself in front of the cameras - leaves the political opponent largely unimpressed and unscathed while being self-destructive in 99% of the cases.

gcc_is_utterly_stupid(var) type of annotations (that initialize to zero instead of the current 'turn off the warning' dangerous construct) would be far better. Albeit even that would in all likelyhood be a rather pointless (but admittedly satisfying) gesture.

Ingo

#9 lore raw
In reply to Rufus & Azrael
Quoted 1 line · Rufus & Azrael

Hi all,

First of all: you really DO NOT WANT to send a message to 4000 people asking for an acknowledgment of receipt.

Quoted 1 line

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Sending 33k of warning messages at once to a generic mailing list is unlikely to get you anywhere. If you really want these warnings to get fixed, you better find the right person to report each warning. Otherwise your report has very little value.

Quoted 13 lines
Quoted 13 lines

drivers/i2c/i2c-core.c: In function ‘i2c_new_device’:
drivers/i2c/i2c-core.c:283: attention : ‘i2c_attach_client’ is deprecated (declared at include/linux/i2c.h:434) drivers/i2c/i2c-core.c: In function ‘i2c_del_adapter’:
drivers/i2c/i2c-core.c:646: attention : ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154) drivers/i2c/i2c-core.c: In function ‘i2c_register_driver’:
drivers/i2c/i2c-core.c:713: attention : ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154) drivers/i2c/i2c-core.c: In function ‘__detach_adapter’:
drivers/i2c/i2c-core.c:780: attention : ‘detach_client’ is deprecated (declared at include/linux/i2c.h:154) drivers/i2c/i2c-core.c: Hors de toute fonction :

Quoted 8 lines
Quoted 8 lines

drivers/i2c/i2c-core.c:876: attention : ‘i2c_attach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:827) drivers/i2c/i2c-core.c:876: attention : ‘i2c_attach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:827) drivers/i2c/i2c-core.c:904: attention : ‘i2c_detach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:879) drivers/i2c/i2c-core.c:904: attention : ‘i2c_detach_client’ is deprecated (declared at drivers/i2c/i2c-core.c:879)

Deprecation warnings are aimed at other developers, users can ignore them safely. They will go away as soon as the deprecated symbols are no longer used.

Signature · 1 line
Jean Delvare
#10 lore raw
Quoted 6 lines · Jean Delvare
Quoted 1 line · Rufus & Azrael

Hi all,

First of all: you really DO NOT WANT to send a message to 4000 people asking for an acknowledgment of receipt.

Quoted 6 lines
Quoted 1 line

Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :

Sending 33k of warning messages at once to a generic mailing list is unlikely to get you anywhere. If you really want these warnings to get fixed, you better find the right person to report each warning. Otherwise your report has very little value.

Also, there's a systematic effort in tip/master to fix all build warnings on all x86 configs that are possible to trigger (with latest GCC):

http://people.redhat.com/mingo/tip.git/README

(the new .29 warnings are not all fixed yet but work is underway)

Ingo