[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <867376179.104878.1616435652773.JavaMail.zimbra@nod.at>
Date: Mon, 22 Mar 2021 18:54:12 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: Rafał Miłecki <zajec5@...il.com>
Cc: Michael Walle <michael@...le.cc>,
linux-mtd <linux-mtd@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Vignesh Raghavendra <vigneshr@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] mtd: require write permissions for locking and badblock
ioctls
----- Ursprüngliche Mail -----
> Von: "Rafał Miłecki" <zajec5@...il.com>
> An: "Michael Walle" <michael@...le.cc>, "linux-mtd" <linux-mtd@...ts.infradead.org>, "linux-kernel"
> <linux-kernel@...r.kernel.org>
> CC: "Miquel Raynal" <miquel.raynal@...tlin.com>, "richard" <richard@....at>, "Vignesh Raghavendra" <vigneshr@...com>,
> "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
> Gesendet: Montag, 22. März 2021 17:39:41
> Betreff: Re: [PATCH] mtd: require write permissions for locking and badblock ioctls
> On 03.03.2021 16:57, Michael Walle wrote:
>> MEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require
>> write permission. Depending on the hardware MEMLOCK might even be
>> write-once, e.g. for SPI-NOR flashes with their WP# tied to GND. OTPLOCK
>> is always write-once.
>>
>> MEMSETBADBLOCK modifies the bad block table.
>>
>> Fixes: f7e6b19bc764 ("mtd: properly check all write ioctls for permissions")
>> Signed-off-by: Michael Walle <michael@...le.cc>
>
> Should be fine for OpenWrt tools to my best knowledge (and quick testing).
>
> Acked-by: Rafał Miłecki <rafal@...ecki.pl>
Nice!
Acked-by: Richard Weinberger <richard@....at>
Thanks,
//richard
Powered by blists - more mailing lists