linux-kernel - Re: 3.0.3 kernel BUG at kernel/timer.c:1035

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110907102425.GA3423@janus>
Date:	Wed, 7 Sep 2011 12:24:25 +0200
From:	Frank van Maarseveen <frankvm@...nkvm.com>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 3.0.3 kernel BUG at kernel/timer.c:1035

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@...el.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@...el.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).

-- 
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/