linux-kernel - Re: Are Section mismatches out of control?

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 1 Feb 2008 14:30:44 +0100 (CET)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Harvey Harrison <harvey.harrison@...il.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux arch <linux-arch@...r.kernel.org>,
	James Bottomley <James.Bottomley@...senPartnership.com>
Subject: Re: Are Section mismatches out of control?

On Fri, 1 Feb 2008, Harvey Harrison wrote:
> On Fri, 2008-02-01 at 03:03 -0800, Andrew Morton wrote:
> > On Fri, 1 Feb 2008 11:47:18 +0100 Sam Ravnborg <sam@...nborg.org> wrote:
> > > James said in a related posting that the Section mismatch
> > > warnings were getting out of control.
> > 
> > eh.  They're easy - the build system tells you about them!
> > 
> > > The list is here:
> > 
> > Question is: why do people keep adding new ones when they are so easy to
> > detect and fix?
> > 
> > Asnwer: because neither they nor their patch integrators are doing adequate
> > compilation testing.
> 
> Because if there already exists more than a handful peoples' eyes glaze
> over and ignore "just one more warning"

Yes.

> Unless they break the build, or if there currently are 0 and they make
> it non-zero, people seem not to care....sad.  Probably the same for
> sparse/checkpatch, "there's plenty already, I can't be bothered to look"

And before, the actual warnings depended a lot on the kernel
configuration, so making the build break was less of an option.
If Sam's improved section mismatch detection turns out to work fine, we
can fix the issues and start to enable breaking of the build in case of
warnings.

BTW, on m68k I get ca. 160 of them. Most seem to originate in
drivers/isdn/. Doesn't look unsurmountable compared to the number of
other compile warnings fixed during the last few years ;-)

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
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/