Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757977AbZANONb (ORCPT ); Wed, 14 Jan 2009 09:13:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753272AbZANONU (ORCPT ); Wed, 14 Jan 2009 09:13:20 -0500 Received: from mail-ew0-f31.google.com ([209.85.219.31]:41029 "EHLO mail-ew0-f31.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751486AbZANONT (ORCPT ); Wed, 14 Jan 2009 09:13:19 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=sEk0qcAh2CHp8d5GqlOmbccrNvtsoB61uXSZZaE+9Cucq8c3KkFdrlLOt7Y2eJTqkx s/TmGc0YJ6ok/TDa1Pi+uX6dtvtV/gQT2LfbAV2XqviQ3YCERH384ICQH8qCV1kuQfUR mrtnjlCCIFIKVpOfPxEyRApFE/37f3BHspTTw= Date: Wed, 14 Jan 2009 14:13:11 +0000 From: Jarek Poplawski To: Peter Zijlstra Cc: Denys Fedoryschenko , Chris Caputo , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Badalian Vyacheslav , Thomas Gleixner Subject: Re: deadlocks if use htb Message-ID: <20090114141311.GA6643@ff.dom.local> References: <20081010090426.GA6054@ff.dom.local> <200901141417.58667.denys@visp.net.lb> <1231937404.14825.4.camel@laptop> <200901141505.46929.denys@visp.net.lb> <20090114131257.GC6117@ff.dom.local> <1231938929.14825.6.camel@laptop> <20090114132603.GD6117@ff.dom.local> <1231939946.14825.9.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1231939946.14825.9.camel@laptop> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 903 Lines: 25 On Wed, Jan 14, 2009 at 02:32:26PM +0100, Peter Zijlstra wrote: > On Wed, 2009-01-14 at 13:26 +0000, Jarek Poplawski wrote: > > > OK, I hope Denys can apply more, but what about others? Without any > > patches the hole seems to be much bigger. > > OK, I read most of this thread on netdev, but didn't find a clear clue > on the specific hrtimer insertion race. There is something at the beginning of this thread, plus earlier threads mostly with Denys as sender, and "htb bug" in the subject. > > Do you have any clear ideas or should I poke at the htb/hrtimer code a > little? > ...And htb code is htb_dequeue(): qdisc_watchdog_schedule(). Jarek P. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/