From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lilium.sigma-star.at ([109.75.188.150]:54568 "EHLO lilium.sigma-star.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423042AbeCBMUF (ORCPT ); Fri, 2 Mar 2018 07:20:05 -0500 From: Richard Weinberger To: Romain Izard Cc: Artem Bityutskiy , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Cyrille Pitchen , linux-mtd@lists.infradead.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND] mtd: ubi: block: Fix error for write access Date: Fri, 02 Mar 2018 13:21:27 +0100 Message-ID: <304002421.gctIWao8Ge@blindfold> In-Reply-To: <20180302111618.22820-1-romain.izard.pro@gmail.com> References: <20180302111618.22820-1-romain.izard.pro@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: linux-block-owner@vger.kernel.org List-Id: linux-block@vger.kernel.org Am Freitag, 2. M�rz 2018, 12:16:18 CET schrieb Romain Izard: > When opening a device with write access, ubiblock_open returns an error > code. Currently, this error code is -EPERM, but this is not the right > value. > > The open function for other block devices returns -EROFS when opening > read-only devices with FMODE_WRITE set. When used with dm-verity, the > veritysetup userspace tool is expecting EROFS, and refuses to use the > ubiblock device. > > Use -EROFS for ubiblock as well. As a result, veritysetup accepts the > ubiblock device as valid. > > Fixes: 9d54c8a33eec (UBI: R/O block driver on top of UBI volumes) > Signed-off-by: Romain Izard > --- > drivers/mtd/ubi/block.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/mtd/ubi/block.c b/drivers/mtd/ubi/block.c > index b210fdb31c98..4533423cf2aa 100644 > --- a/drivers/mtd/ubi/block.c > +++ b/drivers/mtd/ubi/block.c > @@ -242,7 +242,7 @@ static int ubiblock_open(struct block_device *bdev, > fmode_t mode) * in any case. > */ > if (mode & FMODE_WRITE) { > - ret = -EPERM; > + ret = -EROFS; Queued for -next. Thanks, //richard