From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 3
Date: Mon, 3 Nov 2014 13:50:01 -0800 [thread overview]
Message-ID: <20141103214943.GA20210@roeck-us.net> (raw)
In-Reply-To: <20141103161403.79bde878@canb.auug.org.au>
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
next prev parent reply other threads:[~2014-11-03 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 5:14 linux-next: Tree for Nov 3 Stephen Rothwell
2014-11-03 21:50 ` Guenter Roeck [this message]
2014-11-03 23:18 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-11-03 5:19 Stephen Rothwell
2023-11-03 1:55 Stephen Rothwell
2022-11-03 5:21 Stephen Rothwell
2021-11-03 5:48 Stephen Rothwell
2020-11-03 7:19 Stephen Rothwell
2017-11-03 21:03 Kees Cook
2017-11-03 9:28 Stephen Rothwell
2015-11-03 3:47 Stephen Rothwell
2011-11-03 6:20 Stephen Rothwell
2011-11-03 7:29 ` Sedat Dilek
2011-11-03 11:41 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141103214943.GA20210@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox