From: Jens Axboe <axboe@kernel.dk>
To: Jeff Layton <jlayton@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: cfq: oops in __call_for_each_cic
Date: Tue, 10 Aug 2010 12:10:05 -0400 [thread overview]
Message-ID: <4C6179DD.7010000@kernel.dk> (raw)
In-Reply-To: <20100810102718.45bddc9d@tlielax.poochiereds.net>
On 08/10/2010 10:27 AM, Jeff Layton wrote:
> On Tue, 10 Aug 2010 10:22:41 -0400
> Jeff Moyer <jmoyer@redhat.com> wrote:
>
>> Jeff Layton <jlayton@redhat.com> writes:
>>
>>> Saw this oops on my test machine this morning. I rebooted the machine
>>> last night and hadn't done anything on it other than log in this
>>> morning. The kernel here is based on Steve French's git tree, which is
>>> based on Linus' as of Sunday Aug 8th. Last non-cifs commit is:
>>
>> This looks a lot like this bug:
>> https://bugzilla.redhat.com/show_bug.cgi?id=577968
>>
>> See also:
>> http://kerneloops.org/guilty.php?guilty=cfq_free_io_context&version=2.6.34-rc&start=2228224&end=2260991&class=oops
>>
>> It's been around since 2.6.30.8 according to kerneloops.org. If you
>> find that you have a reliable way of reproducing the issue, that would
>> be great.
>>
>
> Ok, thanks -- no clear reproducer so far. This morning was the
> first time I've seen it and it was on the console of my rawhide
> machine. The last thing I did with it was reboot it last night. I
> suspect that the gzip process came from a cron job or something.
What version did you hit it on?
--
Jens Axboe
next prev parent reply other threads:[~2010-08-10 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 10:40 cfq: oops in __call_for_each_cic Jeff Layton
2010-08-10 14:22 ` Jeff Moyer
2010-08-10 14:27 ` Jeff Layton
2010-08-10 16:10 ` Jens Axboe [this message]
2010-08-10 16:35 ` Jeff Layton
2010-08-10 23:58 ` Jens Axboe
2010-08-11 1:23 ` Jeff Layton
2010-08-11 13:23 ` Jens Axboe
2010-08-11 15:41 ` Jeff Moyer
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=4C6179DD.7010000@kernel.dk \
--to=axboe@kernel.dk \
--cc=jlayton@redhat.com \
--cc=jmoyer@redhat.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 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.