From: Wei Gao via ltp <ltp@lists.linux.it>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] move_mount03: check allow to mount beneath top mount
Date: Tue, 26 Dec 2023 10:11:26 -0500 [thread overview]
Message-ID: <ZYrtHnaYJLmyplj5@wegao> (raw)
In-Reply-To: <87zfzga7xj.fsf@suse.de>
On Tue, Nov 14, 2023 at 09:17:15AM +0000, Richard Palethorpe wrote:
> Hello,
>
> Wei Gao via ltp <ltp@lists.linux.it> writes:
>
> This should at least reference the following commit:
>
> commit 6ac392815628f317fcfdca1a39df00b9cc4ebc8b
> Author: Christian Brauner <brauner@kernel.org>
> Date: Wed May 3 13:18:42 2023 +0200
>
> fs: allow to mount beneath top mount
>
> To be honest I am struggling to understand what all of this
> does. However I think that I found some issues with the test which I
> have noted below.
>
Thanks for your pateint review, i also spend a lot of time to recall
my memory for this test case, so i decide to reconstruct this test case
with heavy comments to introduce how this feature work and give every
explaination for each step of test case.
>
>
>
> --
> Thank you,
> Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-12-26 15:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 10:15 [LTP] [PATCH v1] move_mount03: check allow to mount beneath top mount Wei Gao via ltp
2023-11-14 9:17 ` Richard Palethorpe
2023-12-26 15:11 ` Wei Gao via ltp [this message]
2023-12-27 0:04 ` [LTP] [PATCH v2] " Wei Gao via ltp
2023-12-27 14:26 ` Petr Vorel
2023-12-28 2:53 ` Wei Gao via ltp
2023-12-28 2:55 ` [LTP] [PATCH v3] " Wei Gao via ltp
2024-03-06 17:24 ` Martin Doucha
2024-03-20 7:43 ` Petr Vorel
2024-03-20 9:25 ` Martin Doucha
2024-03-20 9:54 ` Petr Vorel
2024-03-21 4:46 ` Petr Vorel
2024-03-22 11:20 ` [LTP] [PATCH v4] " Wei Gao via ltp
2024-05-17 14:48 ` Martin Doucha
2024-06-03 7:38 ` Petr Vorel
2024-06-05 10:59 ` [LTP] [PATCH v5] " Wei Gao via ltp
2025-02-21 10:35 ` Petr Vorel
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=ZYrtHnaYJLmyplj5@wegao \
--to=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
--cc=wegao@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.