From: Vivek Goyal <vgoyal@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
John Stultz <john.stultz@linaro.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Tejun Heo <tj@kernel.org>
Subject: Re: [seqcount] INFO: trying to register non-static key.
Date: Tue, 12 Nov 2013 10:15:41 -0500 [thread overview]
Message-ID: <20131112151541.GD24980@redhat.com> (raw)
In-Reply-To: <20131112100140.GM5056@laptop.programming.kicks-ass.net>
On Tue, Nov 12, 2013 at 11:01:40AM +0100, Peter Zijlstra wrote:
> On Tue, Nov 12, 2013 at 05:41:47PM +0800, Fengguang Wu wrote:
> > On Mon, Nov 11, 2013 at 04:45:51PM +0100, Peter Zijlstra wrote:
> > > On Mon, Nov 11, 2013 at 09:29:27AM +0800, Fengguang Wu wrote:
> > > > Greetings,
> > > >
> > > > I got the below dmesg and the first bad commit is
> > > >
> > > > commit 1ca7d67cf5d5a2aef26a8d9afd789006fa098347
> > > > Author: John Stultz <john.stultz@linaro.org>
> > > > Date: Mon Oct 7 15:51:59 2013 -0700
> > > >
> > > > seqcount: Add lockdep functionality to seqcount/seqlock structures
> > > >
> > >
> > > > [ 4.124336] uli526x: ULi M5261/M5263 net driver, version 0.9.3 (2005-7-29)
> > > > [ 4.128027] Call Trace:
> > > > [ 4.128027] [<7908e744>] ? console_unlock+0x353/0x380
> > > > [ 4.128027] [<79dc7cf2>] dump_stack+0x48/0x60
> > > > [ 4.128027] [<7908953e>] __lock_acquire.isra.26+0x7e3/0xceb
> > > > [ 4.128027] [<7908a1c5>] lock_acquire+0x71/0x9a
> > > > [ 4.128027] [<794079aa>] ? blk_throtl_bio+0x1c3/0x485
> > > > [ 4.128027] [<7940658b>] throtl_update_dispatch_stats+0x7c/0x153
> > >
> > > The below seems to compile with i386-defconfig + CONFIG_CFQ_GROUP_IOSCHED=y
> > >
> > > No idea if it runs properly or not; I seem to have misplaced my i386
> > > root filesystem.
> > >
> > > ---
> > > Subject: block: Employ u64_stats_init()
> > >
> > > Now that seqcounts are lockdep tracked thingies, we need to properly
> > > initialize them, otherwise bad stuff happens.
> >
> > FYI the warning is still there:
> >
> > /kernel/i386-randconfig-j7-11082318/d3516a7318f8e22f5462888fdf9edc8f0f128024
> >
> > +-------------------------------------------------+-------+--------------+--------------+
> > | | v3.12 | 838cc7b488f8 | d3516a7318f8 |
> > +-------------------------------------------------+-------+--------------+--------------+
> > | boot_successes | 129 | 0 | 0 |
> > | boot_failures | 1 | 100 | 100 |
> > | BUG:kernel_early_hang_without_any_printk_output | 1 | | |
> > | INFO:trying_to_register_non-static_key | 0 | 100 | 100 |
> > +-------------------------------------------------+-------+--------------+--------------+
>
> Is that from the exact same spot as before
> (throtl_update_dispatch_stats) or did we hit another one?
[CC tejun]
Peter,
I am wondering if you have to modify blk-throtl.c too to take care
of per cpu stats contained inside throtl_grp.
I see that we allocate per cpu stats but don't do any initializations.
static void tg_stats_alloc_fn(struct work_struct *work)
{
static struct tg_stats_cpu *stats_cpu; /* this fn is non-reentrant */
struct delayed_work *dwork = to_delayed_work(work);
bool empty = false;
alloc_stats:
if (!stats_cpu) {
stats_cpu = alloc_percpu(struct tg_stats_cpu);
if (!stats_cpu) {
/* allocation failed, try again after some time */
schedule_delayed_work(dwork, msecs_to_jiffies(10));
return;
}
}
spin_lock_irq(&tg_stats_alloc_lock);
Thanks
Vivek
next prev parent reply other threads:[~2013-11-12 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 1:29 [seqcount] INFO: trying to register non-static key Fengguang Wu
2013-11-11 15:45 ` Peter Zijlstra
2013-11-11 16:03 ` Vivek Goyal
2013-11-12 9:41 ` Fengguang Wu
2013-11-12 9:50 ` Ingo Molnar
2013-11-12 10:01 ` Peter Zijlstra
2013-11-12 15:03 ` Fengguang Wu
2013-11-12 15:18 ` Fengguang Wu
2013-11-12 15:15 ` Vivek Goyal [this message]
2013-11-12 15:29 ` Peter Zijlstra
2013-11-12 15:46 ` Vivek Goyal
2013-11-13 3:35 ` Fengguang Wu
2013-11-13 3:35 ` John Stultz
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=20131112151541.GD24980@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.