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:   Thu, 13 Jan 2022 11:29:24 +0000
From:   Jon Hunter <>
To:     Lukas Czerner <>,,
        "" <>
Subject: Re: [PATCH v3 12/13] ext4: switch to the new mount api

Hi Lukas,

On 21/10/2021 12:45, Lukas Czerner wrote:
> Add the necessary functions for the fs_context_operations. Convert and
> rename ext4_remount() and ext4_fill_super() to ext4_get_tree() and
> ext4_reconfigure() respectively and switch the ext4 to use the new api.
> One user facing change is the fact that we no longer have access to the
> entire string of mount options provided by mount(2) since the mount api
> does not store it anywhere. As a result we can't print the options to
> the log as we did in the past after the successful mount.
> Signed-off-by: Lukas Czerner <>

I have noticed the following error on -next on various ARM64 platforms 
that we have ...

  ERR KERN /dev/mmcblk1: Can't open blockdev

I have bisected this, to see where this was introduced and bisect is 
pointing to this commit. I have not looked any further so far, but 
wanted to see if you had any ideas/suggestions?



Powered by blists - more mailing lists