linux-kernel - Re: linux-next: Tree for Nov 3

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]

Message-ID: <20141103214943.GA20210@roeck-us.net>
Date:	Mon, 3 Nov 2014 13:50:01 -0800
From:	Guenter Roeck <linux@...ck-us.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for Nov 3

On Mon, Nov 03, 2014 at 04:14:03PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20141031:
> 
> Linus' tree gained a build failure for which I applied a patch.
> 
> The staging tree gained conflicts against the vfs tree.
> 
> The scsi tree gained a build failure so I used the version from
> next-20141031.
> 
> The akpm-current tree lost its build failure.
> 
> Non-merge commits (relative to Linus' tree): 3017
>  2504 files changed, 81573 insertions(+), 104833 deletions(-)
> 
> ----------------------------------------------------------------------------
> 

Something is fishy with this tree. I get either warnings or complete failures
with qemu runs on all platforms.

x86_64:

------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at fs/dcache.c:255 __d_free+0x43/0x50()
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.18.0-rc3-next-20141103-yocto-standard #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014
 0000000000000009 ffff880007c03e38 ffffffff81731601 0000000000000101
 0000000000000000 ffff880007c03e78 ffffffff810484dc ffff880007c03e68
 ffff880006930600 ffff880006930830 000000000000000a 0000000000000000
Call Trace:
 <IRQ>  [<ffffffff81731601>] dump_stack+0x4f/0x7c
 [<ffffffff810484dc>] warn_slowpath_common+0x8c/0xc0
 [<ffffffff8104852a>] warn_slowpath_null+0x1a/0x20
 [<ffffffff81180073>] __d_free+0x43/0x50
 [<ffffffff81098cd1>] rcu_process_callbacks+0x211/0x5c0
 [<ffffffff8104be14>] __do_softirq+0xf4/0x2c0
 [<ffffffff810393d0>] ? rodata_test+0xa0/0xa0
 [<ffffffff8104c1fe>] irq_exit+0x7e/0xa0
 [<ffffffff8173a20a>] smp_apic_timer_interrupt+0x4a/0x60
 [<ffffffff8173898a>] apic_timer_interrupt+0x6a/0x70
 <EOI>  [<ffffffff810393df>] ? start_periodic_check_for_corruption+0xf/0x60
 [<ffffffff810002dc>] ? do_one_initcall+0x8c/0x1c0
 [<ffffffff81080f23>] ? __wake_up+0x53/0x70
 [<ffffffff81ce4126>] kernel_init_freeable+0x14d/0x1e1
 [<ffffffff81ce38fe>] ? do_early_param+0x8d/0x8d
 [<ffffffff8172b240>] ? rest_init+0x90/0x90
 [<ffffffff8172b24e>] kernel_init+0xe/0xf0
 [<ffffffff81737aec>] ret_from_fork+0x7c/0xb0
 [<ffffffff8172b240>] ? rest_init+0x90/0x90

Common theme seems to be the call to rcu_process_callbacks followed by __d_free.

See the qemu logs at http://server.roeck-us.net:8010/builders for more details.

There are also several new build errors.

Error log:
fs/open.c: In function 'SYSC_fchmod':
fs/open.c:530:3: error: implicit declaration of function 'audit_file'
[-Werror=implicit-function-declaration]
   audit_file(f.file);

Guenter
--
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/