[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A35CC249-5F77-4B1A-B68F-8E07A38AB73B@live.com>
Date: Sun, 4 Dec 2022 11:01:49 +0000
From: Aditya Garg <gargaditya08@...e.com>
To: Christoph Hellwig <hch@....de>
CC: Andrew Morton <akpm@...ux-foundation.org>,
"willy@...radead.org" <willy@...radead.org>,
"ira.weiny@...el.com" <ira.weiny@...el.com>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"bvanassche@....org" <bvanassche@....org>,
"keescook@...omium.org" <keescook@...omium.org>,
"songmuchun@...edance.com" <songmuchun@...edance.com>,
"slava@...eyko.com" <slava@...eyko.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] hfsplus: Add module parameter to enable force writes
> On 04-Dec-2022, at 1:37 PM, Christoph Hellwig <hch@....de> wrote:
>
> NAK. Global module options overriding mount options don't make sense.
> If you mount so much write yourself a script, or add the option to the
> configuration of the automounting tool of your choice.
Hi Christoph
My bad I wasn't aware udisks2 now supports custom configuration. I just came to know about this and thus this patch of mine indeed does not make any sense now.
Although, if you think its worth it, the following improvements can be made :-
1. There is no logging showing that writes have been force enabled. We could add that.
2. We could have separate mount options for journaled and locked volumes (although I dunno in what case we get locked volumes).
Powered by blists - more mailing lists