From: Fengguang Wu <fengguang.wu@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
Date: Mon, 28 Oct 2013 20:49:11 +0800 [thread overview]
Message-ID: <20131028124911.GA13923@localhost> (raw)
In-Reply-To: <526DF9A4.70709@redhat.com>
On Mon, Oct 28, 2013 at 01:44:04PM +0800, Jason Wang wrote:
> On 10/24/2013 07:20 AM, Fengguang Wu wrote:
> > Yes it reduces the sleeping function bug:
> >
> > /kernel/x86_64-lkp-CONFIG_SCSI_DEBUG/7c4ed2767afb813493b0a8fb18d666cd44550963
> >
> > +------------------------------------------------------------------------------------+-----------+--------------+--------------+
> > | | v3.12-rc3 | 3ab098df35f8 | 7c4ed2767afb |
> > +------------------------------------------------------------------------------------+-----------+--------------+--------------+
> > | good_boots | 30 | 0 | 93 |
> > | has_kernel_error_warning | 0 | 20 | 7 |
> > | BUG:sleeping_function_called_from_invalid_context_at_kernel/mutex.c | 0 | 20 | |
> > | INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 0 | 0 | 1 |
> > | INFO:task_blocked_for_more_than_seconds | 0 | 0 | 2 |
> > | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 |
> > | Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 |
> > | BUG:kernel_test_crashed | 0 | 0 | 3 |
> > | BUG:kernel_test_hang | 0 | 0 | 1 |
> > +------------------------------------------------------------------------------------+-----------+--------------+--------------+
> >
> > However I'll need to increase tests on v3.12-rc3 to make sure it's not
> > the patch that added the other error messages.
> >
> > Thanks,
> > Fengguang
>
> Thanks, any more update on the result of v3.12-rc3 for this?
Yes, it's confirmed that there are no new error types in 7c4ed2767afb
comparing to v3.12-rc3, so your fix is fine.
/kernel/x86_64-lkp-CONFIG_SCSI_DEBUG/7c4ed2767afb813493b0a8fb18d666cd44550963
+------------------------------------------------------------------------------------+-----------+--------------+--------------+
| | v3.12-rc3 | 3ab098df35f8 | 7c4ed2767afb |
+------------------------------------------------------------------------------------+-----------+--------------+--------------+
| good_boots | 877 | 0 | 93 |
| has_kernel_error_warning | 154 | 20 | 7 |
| BUG:kernel_test_hang | 112 | 0 | 1 |
| INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 1 | 0 | 1 |
| INFO:task_blocked_for_more_than_seconds | 18 | 0 | 2 |
| INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 11 | 0 | 1 |
| Kernel_panic-not_syncing:hung_task:blocked_tasks | 11 | 0 | 1 |
| BUG:kernel_test_crashed | 13 | 0 | 3 |
| Out_of_memory:Kill_process | 9 | | |
| BUG:kernel_early_hang_without_any_printk_output | 1 | | |
| page_allocation_failure:order:,mode | 1 | | |
| Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 2 | | |
| BUG:sleeping_function_called_from_invalid_context_at_kernel/mutex.c | 0 | 20 | |
+------------------------------------------------------------------------------------+-----------+--------------+--------------+
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
Date: Mon, 28 Oct 2013 20:49:11 +0800 [thread overview]
Message-ID: <20131028124911.GA13923@localhost> (raw)
In-Reply-To: <526DF9A4.70709@redhat.com>
On Mon, Oct 28, 2013 at 01:44:04PM +0800, Jason Wang wrote:
> On 10/24/2013 07:20 AM, Fengguang Wu wrote:
> > Yes it reduces the sleeping function bug:
> >
> > /kernel/x86_64-lkp-CONFIG_SCSI_DEBUG/7c4ed2767afb813493b0a8fb18d666cd44550963
> >
> > +------------------------------------------------------------------------------------+-----------+--------------+--------------+
> > | | v3.12-rc3 | 3ab098df35f8 | 7c4ed2767afb |
> > +------------------------------------------------------------------------------------+-----------+--------------+--------------+
> > | good_boots | 30 | 0 | 93 |
> > | has_kernel_error_warning | 0 | 20 | 7 |
> > | BUG:sleeping_function_called_from_invalid_context_at_kernel/mutex.c | 0 | 20 | |
> > | INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 0 | 0 | 1 |
> > | INFO:task_blocked_for_more_than_seconds | 0 | 0 | 2 |
> > | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 |
> > | Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 |
> > | BUG:kernel_test_crashed | 0 | 0 | 3 |
> > | BUG:kernel_test_hang | 0 | 0 | 1 |
> > +------------------------------------------------------------------------------------+-----------+--------------+--------------+
> >
> > However I'll need to increase tests on v3.12-rc3 to make sure it's not
> > the patch that added the other error messages.
> >
> > Thanks,
> > Fengguang
>
> Thanks, any more update on the result of v3.12-rc3 for this?
Yes, it's confirmed that there are no new error types in 7c4ed2767afb
comparing to v3.12-rc3, so your fix is fine.
/kernel/x86_64-lkp-CONFIG_SCSI_DEBUG/7c4ed2767afb813493b0a8fb18d666cd44550963
+------------------------------------------------------------------------------------+-----------+--------------+--------------+
| | v3.12-rc3 | 3ab098df35f8 | 7c4ed2767afb |
+------------------------------------------------------------------------------------+-----------+--------------+--------------+
| good_boots | 877 | 0 | 93 |
| has_kernel_error_warning | 154 | 20 | 7 |
| BUG:kernel_test_hang | 112 | 0 | 1 |
| INFO:rcu_sched_self-detected_stall_on_CPU(t=jiffies_g=c=q=) | 1 | 0 | 1 |
| INFO:task_blocked_for_more_than_seconds | 18 | 0 | 2 |
| INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 11 | 0 | 1 |
| Kernel_panic-not_syncing:hung_task:blocked_tasks | 11 | 0 | 1 |
| BUG:kernel_test_crashed | 13 | 0 | 3 |
| Out_of_memory:Kill_process | 9 | | |
| BUG:kernel_early_hang_without_any_printk_output | 1 | | |
| page_allocation_failure:order:,mode | 1 | | |
| Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 2 | | |
| BUG:sleeping_function_called_from_invalid_context_at_kernel/mutex.c | 0 | 20 | |
+------------------------------------------------------------------------------------+-----------+--------------+--------------+
Thanks,
Fengguang
next prev parent reply other threads:[~2013-10-28 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 2:34 [virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616 Fengguang Wu
2013-10-20 2:34 ` Fengguang Wu
2013-10-22 8:35 ` Jason Wang
2013-10-22 8:35 ` Jason Wang
2013-10-22 8:35 ` Jason Wang
2013-10-23 23:20 ` Fengguang Wu
2013-10-23 23:20 ` Fengguang Wu
2013-10-28 5:44 ` Jason Wang
2013-10-28 5:44 ` Jason Wang
2013-10-28 12:49 ` Fengguang Wu [this message]
2013-10-28 12:49 ` Fengguang Wu
2013-11-03 14:28 ` Fengguang Wu
2013-11-03 14:28 ` Fengguang Wu
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=20131028124911.GA13923@localhost \
--to=fengguang.wu@intel.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.