From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id B826B927 for ; Fri, 9 May 2014 18:08:31 +0000 (UTC) Received: from mail-qc0-f174.google.com (mail-qc0-f174.google.com [209.85.216.174]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 883A520213 for ; Fri, 9 May 2014 18:08:30 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id x13so4907020qcv.19 for ; Fri, 09 May 2014 11:08:29 -0700 (PDT) MIME-Version: 1.0 Sender: roland.dreier@gmail.com In-Reply-To: References: <1399552623.17118.22.camel@i7.infradead.org> From: Roland Dreier Date: Fri, 9 May 2014 11:08:09 -0700 Message-ID: To: Matthew Wilcox Content-Type: text/plain; charset=UTF-8 Cc: linux-nvme@lists.infradead.org, "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] [CORE TOPIC] Device error handling / reporting / isolation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, May 9, 2014 at 10:58 AM, Matthew Wilcox wrote: > I'm hearing a bunch of FUD around NVMe hotplug but precious little in the > way of bug reports! Keith Busch has been doing a stellar job of fixing up > the bugs that he's found, but I have seen precisely zero hotplug bugs > reported to the NVMe mailing list. So put up or shut up. Fair enough, not trying to spread FUD here. The issues we've seen so far have been more around platforms not configured to report PCIe errors properly vs. the NVMe driver itself. - R.