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=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 A0E66C5B57D for ; Tue, 2 Jul 2019 08:14:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 76C442064A for ; Tue, 2 Jul 2019 08:14:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562055269; bh=/hqUavSM9jF40GYQlnoxzOeSzhs5r4KnNGS0tgqpMmw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=T7UKO2aRkKNGS2i0+nG8igUxy9zjBtnK/0UDwjDcQ3hFIhiws3n5KLLGOYW7iS1fb zMAKbQjeG2OQYBuNMqIuHLIUGFZFpM9wViw1KOjwjtpa7/pL+iv2QlIQGd0DstZBXV 3wbZm0b/xRCeLS53T4SfoZDEo3VMn2ddaspFAgvE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728088AbfGBIO2 (ORCPT ); Tue, 2 Jul 2019 04:14:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:34784 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727735AbfGBIO1 (ORCPT ); Tue, 2 Jul 2019 04:14:27 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6FFE520645; Tue, 2 Jul 2019 08:14:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562055266; bh=/hqUavSM9jF40GYQlnoxzOeSzhs5r4KnNGS0tgqpMmw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LY8IBqQZTRTt/uW3FLWUWwDni0+hT5KCwmSW8QMU3nrKeFHQtCL4/XBjNETj8Fye+ Tm1JAYPU8LTyLCTKuseUqdCQ2yaAqitEvkZsga44BQM0XoR/ArXqksiv9PZqK1qRNX wYReplZJP1chTiDrXxc6lWY8IzzAhDd4iDc+imAs= Date: Tue, 2 Jul 2019 10:14:24 +0200 From: Greg KH To: JC Kuo Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu, usb-storage@lists.one-eyed-alien.net, oneukum@suse.com Subject: Re: [PATCH] usb: storage: skip only when uas driver is loaded Message-ID: <20190702081424.GA4162@kroah.com> References: <20190701084848.32502-1-jckuo@nvidia.com> <20190701085248.GA28681@kroah.com> <8e8e8703-8620-b625-4917-bbb8d999caa4@nvidia.com> <20190702044249.GA694@kroah.com> <20190702073432.GA9265@kroah.com> <136cd205-6114-2be5-4244-f6689ce6bf3b@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <136cd205-6114-2be5-4244-f6689ce6bf3b@nvidia.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Tue, Jul 02, 2019 at 03:57:04PM +0800, JC Kuo wrote: > On 7/2/19 3:34 PM, Greg KH wrote: > > > > Footers like this are not allowed on public mailing lists, and forbid me > > to respond to... > > > > Hi Greg, > I am truly sorry for that. I have just figured out how to tell mail server > not to add the footer. Please allow me to query again. > > Since blacklisting uas kernel module is not a good idea and could break UAS > capable storage functionality, although user-space should be blamed for the > improper configuration, do we consider forbidding making uas driver as > module? That means to make CONFIG_USB_UAS a bool option. Step back and try to describe the real problem that you are having here. Why is the kernel responsible for fixing a broken userspace configuration? What UAS devices are not working with Linux that could cause someone to want to blacklist the uas driver and who is telling them to do that? Also see Oliver's response. thanks, greg k-h