linux-kernel - Re: [git pull -tip] headers_check fixes for other architectures

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 1 Feb 2009 17:49:15 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	hskinnemoen@...el.com, cooloney@...nel.org, tony.luck@...el.com,
	ralf@...ux-mips.org, dhowells@...hat.com, matthew@....cx,
	chris@...kel.net, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull -tip] headers_check fixes for other architectures


* Ingo Molnar <mingo@...e.hu> wrote:

> > These patches fixes 41 headers_check warnings as shown in first email.
> 
> Pulled into tip/core/header-fixes, thanks Jaswinder!

These are the remaining ones on x86:

     17 /dev/shm/tip/usr/include/linux/reiserfs_fs.h
     12 /dev/shm/tip/usr/include/linux/soundcard.h
      6 /dev/shm/tip/usr/include/asm/setup.h
      3 /dev/shm/tip/usr/include/linux/nubus.h
      2 /dev/shm/tip/usr/include/linux/in6.h
      1 /dev/shm/tip/usr/include/mtd/jffs2-user.h
      1 /dev/shm/tip/usr/include/linux/socket.h
      1 /dev/shm/tip/usr/include/linux/coda_psdev.h
      1 /dev/shm/tip/usr/include/asm/prctl.h

They are all of the "extern's make no sense in userspace" type. What was the 
verdict, are they worth touching, or should we turn off this warning in 
'make headers_check'?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/