public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jet Chen <jet.chen@intel.com>, Hong Zhiguo <zhiguohong@tencent.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [blk] WARNING: CPU: 0 PID: 300 at kernel/softirq.c:156 _local_bh_enable_ip()
Date: Mon, 21 Apr 2014 19:06:03 -0600	[thread overview]
Message-ID: <5355C07B.4040502@kernel.dk> (raw)
In-Reply-To: <53542E54.2060202@intel.com>

On 2014-04-20 14:30, Jet Chen wrote:
> Hi Zhiguo,
>
> I got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 2c575026fae6e63771bd2a4c1d407214a8096a89
> Author:     Hong Zhiguo <zhiguohong@tencent.com>
> AuthorDate: Wed Nov 20 10:35:05 2013 -0700
> Commit:     Jens Axboe <axboe@kernel.dk>
> CommitDate: Wed Nov 20 15:33:04 2013 -0700
>
>      Update of blkg_stat and blkg_rwstat may happen in bh context.
>      While u64_stats_fetch_retry is only preempt_disable on 32bit
>      UP system. This is not enough to avoid preemption by bh and
>      may read strange 64 bit value.
>          Signed-off-by: Hong Zhiguo <zhiguohong@tencent.com>
>      Acked-by: Tejun Heo <tj@kernel.org>
>      Cc: stable@kernel.org
>      Signed-off-by: Jens Axboe <axboe@kernel.dk>
>
>
>
> +-----------------------------------------------------------+------------+------------+
> |                                                           | 82023bb7f7 | 2c575026fa |
> +-----------------------------------------------------------+------------+------------+
> | boot_successes                                            | 47         | 0          |
> | boot_failures                                             | 13         | 20         |
> | BUG:kernel_boot_hang                                      | 13         | 5          |
> | inconsistent_IN-SOFTIRQ-W-SOFTIRQ-ON-W_usage              | 0          | 15         |
> | backtrace:smpboot_thread_fn                               | 0          | 15         |
> | backtrace:vfs_read                                        | 0          | 9          |
> | backtrace:SyS_read                                        | 0          | 9          |
> | WARNING:CPU:PID:at_kernel/softirq.c:_local_bh_enable_ip() | 0          | 7          |
> | BUG:spinlock_lockup_suspected_on_CPU                      | 0          | 1          |
> | backtrace:do_mount                                        | 0          | 6          |
> | backtrace:SyS_mount                                       | 0          | 6          |
> | backtrace:async_run_entry_fn                              | 0          | 0          |
> +-----------------------------------------------------------+------------+------------+
>
> [   12.318816] WARNING: CPU: 0 PID: 300 at kernel/softirq.c:156 _local_bh_enable_ip+0x34/0x97()

Does this still happen with 3.15-rc2?

-- 
Jens Axboe


  reply	other threads:[~2014-04-22  1:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 20:30 [blk] WARNING: CPU: 0 PID: 300 at kernel/softirq.c:156 _local_bh_enable_ip() Jet Chen
2014-04-22  1:06 ` Jens Axboe [this message]
2014-04-23 11:42   ` Hong zhi guo

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=5355C07B.4040502@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fengguang.wu@intel.com \
    --cc=jet.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhiguohong@tencent.com \
    /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