linux-kernel - Re: Build regressions/improvements in v2.6.36-rc8

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:	Sat, 16 Oct 2010 15:14:42 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: Build regressions/improvements in v2.6.36-rc8

On Sat, 16 Oct 2010 17:31:34 +0200 (CEST) Geert Uytterhoeven wrote:

> 	Hi Stephen,
> 
> On Sat, 16 Oct 2010, Geert Uytterhoeven wrote:
> > 162 regressions:
> > 	src/fs/9p/vfs_inode.c: error: implicit declaration of function 'inode_setattr':  => 1267
> > 	src/include/linux/vgaarb.h: error: asm/vga.h: No such file or directory:  => 34:21
> 
> These two are reported for m68k/allmodconfig:
> http://kisskb.ellerman.id.au/kisskb/buildresult/3387901/, but I cannot
> reproduce them.
> 
> Moreover, there's no call to inode_setattr on line 1267 of
> src/fs/9p/vfs_inode.c.
> The same is true for line 34 of include/linux/vgaarb.h.
> 
> For the second failure, I know it's been fixed since
> 71beefe8c0b9e12ed4ac9fe13b98a035ddeaf8eb.
> 
> Do you know what's happening here?

I can't see why that's happening, but then I can't find a function or macro
named 'inode_setattr' in the -rc8 kernel source tree at all.
Maybe it's a constructed name (i.e., with ##, stringify)?

BTW, do you use LC_ALL=C when doing builds?  I'd like to be able to read
messages like this one:

src/Documentation/spi/spidev_test.c:56: warning: (near initialization for âtrâ): 1 warnings in 1 logs



---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/