Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 295627 - sys-kernel/hardened-sources-2.6.28-r9 generates far to many warnings while compiling
Summary: sys-kernel/hardened-sources-2.6.28-r9 generates far to many warnings while co...
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Hardened (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-04 09:18 UTC by Frederik Schaller
Modified: 2010-01-02 07:48 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederik Schaller 2009-12-04 09:18:28 UTC
A completely fresh stage3 install (AMD64, hardened profile, hardened-sources) generates far too many warnings, like 

include/linux/fsnotify.h: In function 'fsnotify_nameremove':
include/linux/fsnotify.h:80: warning: pointer targets in passing argument 4 of 'inotify_dentry_parent_queue_event' differ in signedness
include/linux/fsnotify.h: In function 'fsnotify_create':
include/linux/fsnotify.h:107: warning: pointer targets in passing argument 4 of 'inotify_inode_queue_event' differ in signedness
include/linux/fsnotify.h:108: warning: pointer targets in passing argument 1 of 'audit_inode_child' differ in signedness
include/linux/fsnotify.h: In function 'fsnotify_link':
include/linux/fsnotify.h:120: warning: pointer targets in passing argument 4 of 'inotify_inode_queue_event' differ in signedness
include/linux/fsnotify.h:122: warning: pointer targets in passing argument 1 of 'audit_inode_child' differ in signedness
include/linux/fsnotify.h: In function 'fsnotify_mkdir':
include/linux/fsnotify.h:132: warning: pointer targets in passing argument 4 of 'inotify_inode_queue_event' differ in signedness
include/linux/fsnotify.h:133: warning: pointer targets in passing argument 1 of 'audit_inode_child' differ in signedness 

Reproducible: Always

Steps to Reproduce:
1. Do a stage 3 AMD64 install
2. emerge kernel hardened-sources-2.6.28-r9
3. make




gcc-config -l
 [1] x86_64-pc-linux-gnu-4.3.4 *
 [2] x86_64-pc-linux-gnu-4.3.4-hardenednopie
 [3] x86_64-pc-linux-gnu-4.3.4-vanilla

emerge --info
Portage 2.1.6.13 (hardened/linux/amd64/10.0, gcc-4.3.4, glibc-2.9_p20081201-r2, 2.6.30-gentoo-r5 x86_64)
=================================================================
System uname: Linux-2.6.30-gentoo-r5-x86_64-Intel-R-_Xeon-R-_CPU_L5410_@_2.33GHz-with-gentoo-1.12.13
Timestamp of tree: Sun, 29 Nov 2009 09:15:01 +0000
app-shells/bash:     4.0_p28
dev-lang/python:     2.6.2-r1
sys-apps/baselayout: 1.12.13
sys-apps/sandbox:    1.6-r2
sys-devel/autoconf:  2.63-r1
sys-devel/automake:  1.10.2
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6a
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo/ ftp://mirror.switch.ch/mirror/gentoo/ "
LDFLAGS="-Wl,-O1"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="acl amd64 berkdb bzip2 cli cracklib crypt cups dri gdbm gpm hardened iconv justify mmx modules mudflap multilib ncurses nls nptl nptlonly openmp pam pcre perl pic pppd python readline reflection session spl sse sse2 ssl symlink sysfs tcpd urandom xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="fbdev glint intel mach64 mga neomagic nv r128 radeon savage sis tdfx trident vesa vga via vmware voodoo"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Comment 1 Dennis Schridde 2009-12-14 09:56:10 UTC
Please change "Product" to "Gentoo Linux". "Bugzilla" is certainly wrong.
Comment 2 Jory A. Pratt gentoo-dev 2009-12-31 01:28:31 UTC
I fail to see what the problem is, we are working to get a much needed update in the tree as soon as it is ready. Where is the bug in a kernel that compiles and works as expected?
Comment 3 Jory A. Pratt gentoo-dev 2009-12-31 02:25:12 UTC
mpango and myself both agree there is no bug here, the warnings are just that warnings. 
Comment 4 Dennis Schridde 2009-12-31 08:46:38 UTC
(In reply to comment #2)
> I fail to see what the problem is, we are working to get a much needed update
> in the tree as soon as it is ready. Where is the bug in a kernel that compiles
> and works as expected?
I assume the intention of the bug author was to suggest that warnings often mean possibly unexpected and erroneous behaviour in corner cases.
Comment 5 Frederik Schaller 2010-01-02 07:48:56 UTC
> I assume the intention of the bug author was to suggest that warnings often
> mean possibly unexpected and erroneous behaviour in corner cases.
This was excatly my itention. The kernel is working as expected, so there is no problem (from a technical point of view). If you're going to install production systems and you have thousends of this warnings you'll likely sleep not very well ;-)