From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7294FC10F11 for ; Wed, 10 Apr 2019 08:02:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 459CD20818 for ; Wed, 10 Apr 2019 08:02:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727256AbfDJICU (ORCPT ); Wed, 10 Apr 2019 04:02:20 -0400 Received: from mx2.suse.de ([195.135.220.15]:48150 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727212AbfDJICU (ORCPT ); Wed, 10 Apr 2019 04:02:20 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 189A8B02B; Wed, 10 Apr 2019 08:02:19 +0000 (UTC) Message-ID: <1554883329.21725.1.camel@suse.com> Subject: Re: Bug: VHCI + USB 3.0 From: Oliver Neukum To: Alan Stern , Seth Bollinger Cc: Ming Lei , Jens Axboe , linux-block , USB list Date: Wed, 10 Apr 2019 10:02:09 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Di, 2019-04-09 at 15:57 -0400, Alan Stern wrote: > On Tue, 9 Apr 2019, Bollinger, Seth wrote: > > > I will do that as a test. However, I’m concerned that we’re solving only a specific case. Won’t it fail in a similar way if a different subsystem does the same thing (USB modem or video drivers, etc.)? > > Those other drivers don't use the block device interface, as far as I > know. So they would have to use other methods for addressing the > potential problems in any case. usb-storage is perhaps distinct in > that it doesn't generate the scatter-gather lists that it uses, but > instead has to work with whatever the block layer provides. UAS, too. But I can pick up the corresponding fix. Are you sure about sound though? Regards Oliver