linux-ext4 - Re: Unexpected writes seen on a Read-only, DAX enabled EXT4 fs

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 12 Sep 2017 11:03:49 +0200
From:   Simon Ruderich <simon@...erich.org>
To:     Andreas Dilger <adilger@...ger.ca>
Cc:     Ross Zwisler <ross.zwisler@...ux.intel.com>,
        Soccer Liu <soccer_liu@...oo.com>, linux-ext4@...r.kernel.org,
        "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
Subject: Re: Unexpected writes seen on a Read-only, DAX enabled EXT4 fs

On Mon, Sep 11, 2017 at 02:31:41PM -0600, Andreas Dilger wrote:
> On Sep 11, 2017, at 12:21 PM, Ross Zwisler wrote:
>>
>> On Sat, Sep 09, 2017 at 05:10:26PM +0000, Soccer Liu wrote:
>>> [snip]
>>>
>>> Based on the following Mount documentation below, I did mount this ext fs
>>> with ro and noloadAre there any other options that I could use to totally
>>> eliminate those unexpected writes?
>
> [snip]
>
> Also, ext4 journal recovery will be done on the filesystem regardless of
> whether it is mounted read-only or not.

I thought the noload option should prevent journal recovery and
thus be truly read-only. At least it worked on a read-only device
for me.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)