From: Jeff Moyer <jmoyer@redhat.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.5.1: WARNING: at include/linux/iocontext.h:140 copy_process.part.56+0x1041/0x1190()
Date: Thu, 16 Aug 2012 10:05:39 -0400 [thread overview]
Message-ID: <x498vdf7wzw.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CAO9zADxc3fVUwRhxzbirQvjVLjun3_Dt150KYakoCUOzB3aksg@mail.gmail.com> (Justin Piszcz's message of "Wed, 15 Aug 2012 20:04:12 -0400")
Justin Piszcz <jpiszcz@lucidpixels.com> writes:
> Hi,
>
> Kernel: 3.5.1 x86_64
> Just FYI, this may have been due to an NFS issue (remote host turned
> off during dump possibly) but reporting just incase:
>
> [41793.725267] ------------[ cut here ]------------
> [41793.725273] WARNING: at include/linux/iocontext.h:140
> copy_process.part.56+0x1041/0x1190()
> [41793.725274] Hardware name: X9SCL/X9SCM
> [41793.725276] Pid: 20378, comm: dump Not tainted 3.5.1 #2
> [41793.725276] Call Trace:
> [41793.725279] [<ffffffff8102f0d5>] warn_slowpath_common+0x75/0xb0
> [41793.725280] [<ffffffff8102f1e5>] warn_slowpath_null+0x15/0x20
> [41793.725282] [<ffffffff8102e371>] copy_process.part.56+0x1041/0x1190
> [41793.725283] [<ffffffff8102e62b>] do_fork+0x13b/0x2f0
> [41793.725285] [<ffffffff8103cc02>] ? recalc_sigpending+0x12/0x30
> [41793.725287] [<ffffffff8103f4aa>] ? __set_current_blocked+0x3a/0x60
> [41793.725290] [<ffffffff8100a1e3>] sys_clone+0x23/0x30
> [41793.725293] [<ffffffff815c0a33>] stub_clone+0x13/0x20
> [41793.725294] [<ffffffff815c07e6>] ? system_call_fastpath+0x1a/0x1f
> [41793.725295] ---[ end trace 6afd1df8f82f60e4 ]---
This should be fixed by the following:
commit 4638a83e8615de9c16c39dfed234951d0f468cf1
Author: Olof Johansson <olof@lixom.net>
Date: Wed Aug 1 12:17:27 2012 +0200
block: uninitialized ioc->nr_tasks triggers WARN_ON
prev parent reply other threads:[~2012-08-16 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 0:04 Justin Piszcz
2012-08-16 14:05 ` Jeff Moyer [this message]
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=x498vdf7wzw.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®