linux-ext4 - Re: [PATCH v3 12/13] ext4: switch to the new mount api

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: <2d22b1b7-0091-260a-b86e-ad55a26e320e@nvidia.com>
Date:   Fri, 14 Jan 2022 09:40:19 +0000
From:   Jon Hunter <jonathanh@...dia.com>
To:     Lukas Czerner <lczerner@...hat.com>
Cc:     linux-ext4@...r.kernel.org, tytso@....edu,
        linux-fsdevel@...r.kernel.org,
        "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH v3 12/13] ext4: switch to the new mount api


On 13/01/2022 16:10, Jon Hunter wrote:

...

> OK, I see what is happening. It appears that our test harness always 
> tries to mount a device called /dev/mmcblk1. Prior to this change there 
> was not kernel error generated and looking at the logs I would see ...
> 
> mount: /mnt: special device /dev/mmcblk1 does not exist.
> 
> Following this change, now a kernel warning is generated and I see ...
> 
> [  137.078994] /dev/mmcblk1: Can't open blockdev
> mount: /mnt: special device /dev/mmcblk1 does not exist.
> 
> So there is a change in behaviour but at the same time the error looks 
> correct. So sorry for the false-positive.


Looking some more, previously, mount_bdev was being called and this has ...

         bdev = blkdev_get_by_path(dev_name, mode, fs_type);
         if (IS_ERR(bdev))
                 return ERR_CAST(bdev);

And now we are calling get_tree_bdev() and this has ...

         bdev = blkdev_get_by_path(fc->source, mode, fc->fs_type);
         if (IS_ERR(bdev)) {
                 errorf(fc, "%s: Can't open blockdev", fc->source);
                 return PTR_ERR(bdev);
         }

Hence, the difference. I was interested to know what had changed.

Cheers
Jon

-- 
nvpublic