linux-kernel - Re: How to register block device as read-only

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0707281343140.15125@fbirervta.pbzchgretzou.qr>
Date:	Sat, 28 Jul 2007 13:43:58 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Bernd Petrovitsch <bernd@...mix.at>
cc:	beck0778@....edu, linux-kernel@...r.kernel.org
Subject: Re: How to register block device as read-only


On Jul 28 2007 13:36, Bernd Petrovitsch wrote:
>
>Unless I misunderstand the question, the "write" and "writev" function
>of the "struct file_operations" should return an appropriate error value
>(which is here -EACCES).
>You may think of returning an error in the "open" if someone wants to
>open it to write to it (so that the must open it read-only).
>But I don't know if that is common practice or not (or even disliked) as
>it may interfere with not properly implemented tools which open devices
>read-write even if they never write to it.

Yes it is, I believe. When mount(8) gets an error from mount(2),
it retries with MS_RDONLY enabled.


	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/