Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4950552imm; Fri, 18 May 2018 13:36:08 -0700 (PDT) X-Google-Smtp-Source: AB8JxZowXq/U60JMVF12Uk2CDYBx99cG4ADPQbLuKKtli7Ibng+6ftXFWzRSKDtYeaJmE9UMZ7QV X-Received: by 2002:a17:902:a60d:: with SMTP id u13-v6mr11045712plq.40.1526675768365; Fri, 18 May 2018 13:36:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526675768; cv=none; d=google.com; s=arc-20160816; b=0MgcqyHqM8xpMjQaUCrEozeqHj4yCdY4f7QjJXMQDPfcg80CD3thtchWO9g9KPrDjG CRxdLj/2rTyJ329ibmHFVa9S9/RTzDANMdO1aUySBnDNe7ohCHk253gU+7TIcyoBhxZJ B54vEwJ6nydoNYkg3wEdgcn/zMpNUv0bVYvoQ0lG3DmvoJxBLLAMcbxENyyQTUx0//zV t3ENUtjJ52BD/LcbuZdaAqcR6duAvzudY/BA34290SdcUXKJJjPRp1aKP3NiUiO5gPgz xu3HkZ/WoDRXAb2Afmefc6OoiyvFYbBCIEKS5NSIxV+mPYoU7w31zR0537+dBX5HFutO LMMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:in-reply-to :subject:cc:to:from:date:arc-authentication-results; bh=hbGRLiHpUHdRpT+EdnfSztHQ467QfrTdGhuiLjXPcXw=; b=fmc+MHv7TvfPqPvJtTgqcnac6+W8x0LkWggNitsG3pRFoazMqsrJRGNTkeY/kz5BkP dhnoZ9apars0cRnc5hYqqUGmGod9cyjZnzjeFo/nz7oYl72rzsYOtRcVAY49UBuo4LDk YlGih1ekHzCef1kLeuK+dS9TkOTGx0p7w5TCZB64ozEyowmUrfM4hAUl3/P+KKU1pIoP I1drKHFUJxFjDrYk+5o8Cp3f29COqMxBu6cFFCsRIpnxd1r6QX+2AUwnjKoB4PZTimB3 Y/42wq7IdHhWbADJSmws383GnL446va1vOxvVqE/YmYvDVY8tNxc4sHe6/SoZVwjOR2h bnSw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f11-v6si8432882plj.58.2018.05.18.13.35.54; Fri, 18 May 2018 13:36:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751969AbeERUfX (ORCPT + 99 others); Fri, 18 May 2018 16:35:23 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:43620 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751156AbeERUfT (ORCPT ); Fri, 18 May 2018 16:35:19 -0400 Received: (qmail 8684 invoked by uid 2102); 18 May 2018 16:35:17 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 May 2018 16:35:17 -0400 Date: Fri, 18 May 2018 16:35:17 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Alexander Kappner cc: Oliver Neukum , , , , Subject: Re: [PATCH] usb-storage: Add quirks to make G-Technology "G-Drive" work In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 18 May 2018, Alexander Kappner wrote: > Further debugging shows that the code that causes the device to hang is in > drivers/scsi/sd.c:2698. So the reason why usb-storage works and UAS does > not is because the device setting both skip_ms_page_3f=1 and > skip_ms_page_8=1 is required. The US_FL_NO_WP_DETECT flag does the former, > and usb-storage (but not UAS) by default does the latter > (drivers/usb/storage/scsiglue.c:198): > > /* > * A number of devices have problems with MODE SENSE for > * page x08, so we will skip it. > */ > sdev->skip_ms_page_8 = 1; > > > Forcing both skip_ms_page_3f and skip_ms_page_8 to 1 results in UAS and > usb-storage working. Oliver's code only set skip_ms_page_3f. Good detective work! > Do we want a patch to introduce a quirk flag for skip_ms_page_8, similar to > the US_FL_NO_WP_DETECT quirk bit for skip_ms_page_3f? This may even resolve > the issues with other devices in unusual_uas.h that currently have all UAS > support disabled. I'd be happy to write the patch, but I'm not sure we want > to reserve a quirk bit for what's currently only a single device known to > have this issue. Please advise. Yes, I think we want a patch. Unless Oliver disagrees, please go ahead and prepare one. Alan Stern