From: Frank van Maarseveen <frankvm@frankvm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Lin Ming <ming.m.lin@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: 3.0.3 kernel BUG at kernel/timer.c:1035
Date: Tue, 20 Sep 2011 15:16:16 +0200 [thread overview]
Message-ID: <20110920131615.GA13278@janus> (raw)
In-Reply-To: <20110907143006.0d0922dd.akpm@linux-foundation.org>
On Wed, Sep 07, 2011 at 02:30:06PM -0700, Andrew Morton wrote:
> On Wed, 07 Sep 2011 20:36:19 +0800
> Lin Ming <ming.m.lin@intel.com> wrote:
>
> > On Wed, 2011-09-07 at 18:24 +0800, Frank van Maarseveen wrote:
> > > On Tue, Sep 06, 2011 at 10:48:38PM +0800, Lin Ming wrote:
> > > > Does below patch help?
> > > >
> > > > >From a98b874437f871d5ecc3f6fe409b2b474b1f2731 Mon Sep 17 00:00:00 2001
> > > > From: Lin Ming <ming.m.lin@intel.com>
> > > > Date: Tue, 6 Sep 2011 22:45:43 +0800
> > > > Subject: [PATCH] block: delete bdi writeback wakup_timer in blk_cleanup_queue()
> > > >
> > > > Signed-off-by: Lin Ming <ming.m.lin@intel.com>
> > > > ---
> > > > block/blk-core.c | 1 +
> > > > 1 files changed, 1 insertions(+), 0 deletions(-)
> > > >
> > > > diff --git a/block/blk-core.c b/block/blk-core.c
> > > > index 90e1ffd..22529a3 100644
> > > > --- a/block/blk-core.c
> > > > +++ b/block/blk-core.c
> > > > @@ -363,6 +363,7 @@ void blk_cleanup_queue(struct request_queue *q)
> > > > blk_sync_queue(q);
> > > >
> > > > del_timer_sync(&q->backing_dev_info.laptop_mode_wb_timer);
> > > > + del_timer_sync(&q->backing_dev_info.wb.wakeup_timer);
> > > > mutex_lock(&q->sysfs_lock);
> > > > queue_flag_set_unlocked(QUEUE_FLAG_DEAD, q);
> > > > mutex_unlock(&q->sysfs_lock);
> > > > --
> > > > 1.7.2.3
> > > >
> > >
> > > No, bug still present. Stack trace is the same and I double checked that
> > > it was the new kernel (this time with a lot more debug enabled).
> >
> > Thanks for test.
> > I'll try to reproduce this bug.
>
> Probably this will "fix" it:
>
> --- a/block/blk-sysfs.c~a
> +++ a/block/blk-sysfs.c
> @@ -4,6 +4,7 @@
> #include <linux/kernel.h>
> #include <linux/slab.h>
> #include <linux/module.h>
> +#include <linux/timer.h>
> #include <linux/bio.h>
> #include <linux/blkdev.h>
> #include <linux/blktrace_api.h>
> @@ -486,7 +487,7 @@ static void blk_release_queue(struct kob
> __blk_queue_free_tags(q);
>
> blk_trace_shutdown(q);
> -
> + del_timer_sync(&q->backing_dev_info.wb.wakeup_timer);
> bdi_destroy(&q->backing_dev_info);
> kmem_cache_free(blk_requestq_cachep, q);
> }
> _
>
> Jens, can you please take a look at this regression?
> blk_release_queue() is freeing a pending timer.
Yep, this fixes it. This is the recipe I used for triggering the issue
on 3.0.4 (it can probably be simplified):
- mount an ext[34] formatted USB stick read-write on /mnt, preloaded
with a (64k) file "bar" in subdirectory "foo".
- cat /mnt/foo/bar >/dev/null
- sleep 30 # or more
- unplug USB stick
- issue an "umount -l -f /mnt"
After playing with the 30 second delay parameter (to get more details) the
kernel somehow ended in a state where the bug was no longer reproducable.
A reboot made the recipe work again.
Thanks,
--
Frank
prev parent reply other threads:[~2011-09-20 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 13:02 3.0.3 kernel BUG at kernel/timer.c:1035 Frank van Maarseveen
2011-08-30 9:08 ` Frank van Maarseveen
2011-09-02 8:10 ` Andrew Morton
2011-09-05 12:38 ` Frank van Maarseveen
[not found] ` <CAF1ivSYui_=tHbxHiy15a9wfiphHcpoY+J1MmAJ=dMQsAfEVLw@mail.gmail.com>
2011-09-06 14:48 ` Lin Ming
2011-09-07 10:24 ` Frank van Maarseveen
2011-09-07 12:36 ` Lin Ming
2011-09-07 21:30 ` Andrew Morton
2011-09-09 14:21 ` Lin Ming
2011-09-10 8:41 ` Frank van Maarseveen
2011-09-20 13:16 ` Frank van Maarseveen [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=20110920131615.GA13278@janus \
--to=frankvm@frankvm.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.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