From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751447AbdB1TY5 (ORCPT ); Tue, 28 Feb 2017 14:24:57 -0500 Received: from mail-yw0-f182.google.com ([209.85.161.182]:34426 "EHLO mail-yw0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751334AbdB1TYz (ORCPT ); Tue, 28 Feb 2017 14:24:55 -0500 Date: Tue, 28 Feb 2017 14:23:05 -0500 From: Tejun Heo To: Dmitry Vyukov Cc: linux-ide@vger.kernel.org, LKML , syzkaller Subject: Re: ata: WARNING in ata_sff_qc_issue Message-ID: <20170228192305.GI15287@htj.duckdns.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Tue, Feb 28, 2017 at 03:33:48PM +0100, Dmitry Vyukov wrote: > If the WARNING is merely to inform user about invalid protocol, please > issue a single line pr_err without the stack trace (invalid protocol > value may be more interesting). Yeah, the warning is harmless. The code was written before passthrough support and just assumed that nobody higher up in the stack should be issuing unsupported protocols and warned on such cases as a precaution. I'm just gonna drop the WARN. The error code to sg command should be enough to indicate the failure. Thanks. -- tejun