From: "Alexander Beregalov" <a.beregalov@gmail.com>
To: "Jens Axboe" <jens.axboe@oracle.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: next-20081215: kernel BUG at block/cfq-iosched.c:1243
Date: Mon, 15 Dec 2008 23:29:17 +0300 [thread overview]
Message-ID: <a4423d670812151229ua6f2d67u61ca5e13534fede8@mail.gmail.com> (raw)
In-Reply-To: <20081215201836.GM32491@kernel.dk>
2008/12/15 Jens Axboe <jens.axboe@oracle.com>:
> On Mon, Dec 15 2008, Alexander Beregalov wrote:
>> 2008/12/15 Jens Axboe <jens.axboe@oracle.com>:
>> > On Mon, Dec 15 2008, Alexander Beregalov wrote:
>> >> 2008/12/15 Jens Axboe <jens.axboe@oracle.com>:
>> >> >> [ 23.080733] kernel BUG at block/cfq-iosched.c:1243!
>> >> >> [ 23.080733] invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>> >>
>> >> > Odd, is it reproducible? What is your .config?
>> >> Yes, it is
>> >>
>> >> Config is in attach
>> >
>> > It's weird, because the only change for CFQ in that area is the one
>> > below. Does the oops go away if you back this out?
>> Yes, it can boot without the patch, no oops.
>
> OK, dumb error. Please try this instead, on top of -next:
It works without oopses.
>
> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> index 8a2485d..e8525fa 100644
> --- a/block/cfq-iosched.c
> +++ b/block/cfq-iosched.c
> @@ -1322,7 +1322,6 @@ static void cfq_exit_single_io_context(struct io_context *ioc,
> smp_read_barrier_depends();
> if (cic->key)
> __cfq_exit_single_io_context(cfqd, cic);
> - __cfq_exit_single_io_context(cfqd, cic);
>
> spin_unlock_irqrestore(q->queue_lock, flags);
> }
>
> --
> Jens Axboe
>
>
prev parent reply other threads:[~2008-12-15 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 18:29 Alexander Beregalov
2008-12-15 18:32 ` Jens Axboe
2008-12-15 18:38 ` Alexander Beregalov
2008-12-15 18:44 ` Jens Axboe
2008-12-15 20:09 ` Alexander Beregalov
2008-12-15 20:18 ` Jens Axboe
2008-12-15 20:29 ` Alexander Beregalov [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=a4423d670812151229ua6f2d67u61ca5e13534fede8@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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®