From: Jon Hunter <jonathanh@nvidia.com>
To: Lukas Czerner <lczerner@redhat.com>,
linux-ext4@vger.kernel.org, tytso@mit.edu
Cc: linux-fsdevel@vger.kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v3 12/13] ext4: switch to the new mount api
Date: Thu, 13 Jan 2022 11:29:24 +0000 [thread overview]
Message-ID: <286d36c9-e9ab-b896-e23c-2a95c6385817@nvidia.com> (raw)
In-Reply-To: <20211021114508.21407-13-lczerner@redhat.com>
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 <lczerner@redhat.com>
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?
Cheers
Jon
--
nvpublic
next parent reply other threads:[~2022-01-13 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211021114508.21407-1-lczerner@redhat.com>
[not found] ` <20211021114508.21407-13-lczerner@redhat.com>
2022-01-13 11:29 ` Jon Hunter [this message]
2022-01-13 12:08 ` [PATCH v3 12/13] ext4: switch to the new mount api Lukas Czerner
2022-01-13 15:06 ` Jon Hunter
2022-01-13 16:10 ` Jon Hunter
2022-01-14 9:40 ` Jon Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=286d36c9-e9ab-b896-e23c-2a95c6385817@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox