Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	chris.zjh@huawei.com, tytso@mit.edu, adilger.kernel@dilger.ca,
	viro@zeniv.linux.org.uk, jack@suse.cz
Subject: Re: [PATCH v2] fs: ext4: support relative path for `journal_path` in mount option.
Date: Wed, 25 Sep 2024 10:24:16 +0200	[thread overview]
Message-ID: <20240925-tagebuch-rosig-720884b18e71@brauner> (raw)
In-Reply-To: <20240925015624.3817878-1-lihongbo22@huawei.com>

On Wed, 25 Sep 2024 09:56:24 +0800, Hongbo Li wrote:
> The `fs_lookup_param` did not consider the relative path for
> block device. When we mount ext4 with `journal_path` option using
> relative path, `param->dirfd` was not set which will cause mounting
> error.
> 
> This can be reproduced easily like this:
> 
> [...]

Applied to the vfs.misc.v6.13 branch of the vfs/vfs.git tree.
Patches in the vfs.misc.v6.13 branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc.v6.13

[1/1] fs: ext4: support relative path for `journal_path` in mount option.
      https://git.kernel.org/vfs/vfs/c/457f7b53e736

      parent reply	other threads:[~2024-09-25  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25  1:56 [PATCH v2] fs: ext4: support relative path for `journal_path` in mount option Hongbo Li
2024-09-25  2:09 ` Al Viro
2024-09-25  2:32   ` Hongbo Li
2024-09-25  7:51 ` Jan Kara
2024-09-25  8:01   ` Hongbo Li
2024-09-25  8:21   ` Christian Brauner
2024-09-25  8:24 ` Christian Brauner [this message]

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=20240925-tagebuch-rosig-720884b18e71@brauner \
    --to=brauner@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=chris.zjh@huawei.com \
    --cc=jack@suse.cz \
    --cc=lihongbo22@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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