linux-kernel - Re: [PATCH] inet: Initialize per-netns inetpeer roots in net/ipv{4,6}/route.c

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-next>] [day] [month] [year] [list]

Message-ID: <20120610031634.GA10032@localhost>
Date:	Sun, 10 Jun 2012 11:16:34 +0800
From:	Fengguang Wu <wfg@...ux.intel.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, gaofeng@...fujitsu.com,
	containers@...ts.linux-foundation.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] inet: Initialize per-netns inetpeer roots in
 net/ipv{4,6}/route.c

On Sat, Jun 09, 2012 at 07:04:51PM -0700, David Miller wrote:
> From: Fengguang Wu <wfg@...ux.intel.com>
> Date: Sun, 10 Jun 2012 09:58:32 +0800
> 
> > It triggers some warnings:
> > 
> > WARNING: net/ipv6/ipv6.o(.text+0x1049c): Section mismatch in reference from the function ip6_route_cleanup() to the variable .init.data:ipv6_inetpeer_ops
> 
> This should fix it:

Yes it worked.

Tested-by: Fengguang Wu <wfg@...ux.intel.com>

In long run, such build-fix patches can also be auto tested and
reported, somehow in this way. You just create a temporary branch
named "0day-XXXXXX" and push the build-fix patch there. After a while
my robot script will pull and build test it. When finished, it will
recognize the "0day" pattern in the branch name and then
*unconditionally* report back.

"unconditionally" means it will

- report build failure as well as build success
- report new error/warnings as well as old ones

Upon receiving the success/failure notification, you can then proceed
to either merge the commit to the main branch, or update the commit in
place to restart the test. This should work much more fluently than
waiting for me to manually test some emailed patch. Not only I may be
sleeping at the time, but also I'm sending out build failure reports
almost *every day*. It would be a burden for me to manually test out
fixes every day...

Thanks,
Fengguang
--
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/