From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752858AbcBLSuQ (ORCPT ); Fri, 12 Feb 2016 13:50:16 -0500 Received: from mga09.intel.com ([134.134.136.24]:14452 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752591AbcBLSuM (ORCPT ); Fri, 12 Feb 2016 13:50:12 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,436,1449561600"; d="scan'208";a="651376143" Date: Fri, 12 Feb 2016 18:50:10 +0000 From: Keith Busch To: Ming Lei Cc: Sasha Levin , Jens Axboe , Christoph Hellwig , jonathan.derrick@intel.com, LKML , linux-block@vger.kernel.org Subject: Re: blk: accessing invalid memory with "blk-mq: dynamic h/w context count" Message-ID: <20160212185010.GA28832@localhost.localdomain> References: <56BD7088.1020908@oracle.com> <20160212162435.1e809790@tom-T450> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160212162435.1e809790@tom-T450> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 12, 2016 at 04:24:35PM +0800, Ming Lei wrote: > On Fri, 12 Feb 2016 00:41:28 -0500 > Hi Sasha, > > It should be about timing of setting q->mq_ops, and > I believe the following patch may fix the issue, could > you give a test? Thanks, Ming, that looks better and looks like the same as the 0-day failure from when this was posted a couple months ago. I thought this was potentially risky looking, but haven't had time to make changes. I also didn't see that this was applied yet either. I've a broken filter moving important emails to the junk... On the plus side, the exposure led to a potential fix.