Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751193Ab1DOEPD (ORCPT ); Fri, 15 Apr 2011 00:15:03 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:33358 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750725Ab1DOEPB (ORCPT ); Fri, 15 Apr 2011 00:15:01 -0400 Date: Fri, 15 Apr 2011 00:14:55 -0400 From: Christoph Hellwig To: Linus Torvalds Cc: Borislav Petkov , Jens Axboe , Linux Kernel Mailing List Subject: Re: Linux 2.6.39-rc3 Message-ID: <20110415041455.GA27928@infradead.org> References: <20110414202445.GA6173@liondog.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1195 Lines: 25 On Thu, Apr 14, 2011 at 01:55:02PM -0700, Linus Torvalds wrote: > On Thu, Apr 14, 2011 at 1:24 PM, Borislav Petkov wrote: > > > > Yep, I had to hit a buglet too. Looks like block layer, ->request_fn > > (do_ide_request) called in IRQ disabled region. Process is blkid, i.e. > > some udev helper. Kernel is -rc3 + Joerg's USB quirk fix which should be > > unrelated. > > I think this particular backtrace should be fixed by commit > 6631e635c65d ("block: don't flush plugged IO on forced preemtion > scheduling"), although even without preempt scheduling, I don't think > it's at all ok to sleep inside __blk_run_queue. > > Jens? Even from a _regular_ schedule, it would not be ok if we end up > sleeping - we're caching things like the request-queue, and we have > preempt_disable() inside the scheduler for a very good reason. Jens already has a fix in his tree to always offload the block I/O submission to blockd for this case. -- 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/