From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:58311 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726138AbgKAK1k (ORCPT ); Sun, 1 Nov 2020 05:27:40 -0500 Date: Sun, 1 Nov 2020 11:27:35 +0100 From: Christoph Hellwig Subject: Re: [PATCH 02/11] mtip32xx: return -ENOTTY for all unhanled ioctls Message-ID: <20201101102735.GA26447@lst.de> References: <20201031085810.450489-1-hch@lst.de> <20201031085810.450489-3-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-ID: To: Jens Axboe Cc: Christoph Hellwig , Ilya Dryomov , Song Liu , Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Stefan Haberland , Jan Hoeppner , linux-block@vger.kernel.org, ceph-devel@vger.kernel.org, linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org, linux-mtd@lists.infradead.org, linux-s390@vger.kernel.org On Sat, Oct 31, 2020 at 08:58:52AM -0600, Jens Axboe wrote: > On 10/31/20 2:58 AM, Christoph Hellwig wrote: > > -ENOTTY is the convention for "driver does not support this ioctl". > > Use it properly in mtip32xx instead of the bogys -EINVAL. > > While that's certainly true, there is a risk in making a change like this > years after the fact. Not that I expect there are any mtip32xx users > left at this point, but... -ENOTTY is what most drivers return. That being said we can keep the old behavior, so if you prepfer that I can respin to do that.