public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5] move_mount03: check allow to mount beneath top mount
Date: Fri, 21 Feb 2025 11:35:19 +0100	[thread overview]
Message-ID: <20250221103519.GA2764810@pevik> (raw)
In-Reply-To: <20240605105919.10123-1-wegao@suse.com>

Hi Wei,

merged with adding 6ac392815628f linux-git tag and formatting changes.
Thank you!

Kind regards,
Petr

+++ include/lapi/fsmount.h
@@ -114,14 +114,14 @@ static inline int mount_setattr(int dirfd, const char *from_pathname, unsigned i
 }
 #endif /* HAVE_MOUNT_SETATTR */
 
-#ifndef MOVE_MOUNT_BENEATH
-#define MOVE_MOUNT_BENEATH 		0x00000200
-#endif /* MOVE_MOUNT_BENEATH */
-
 /*
  * New headers added in kernel after 5.2 release, create them for old userspace.
 */
 
+#ifndef MOVE_MOUNT_BENEATH
+# define MOVE_MOUNT_BENEATH 		0x00000200
+#endif
+
 #ifndef OPEN_TREE_CLONE
 
 /*
diff --git testcases/kernel/syscalls/move_mount/move_mount03.c testcases/kernel/syscalls/move_mount/move_mount03.c
index ad5c8b9ed5..a9429af7a0 100644
--- testcases/kernel/syscalls/move_mount/move_mount03.c
+++ testcases/kernel/syscalls/move_mount/move_mount03.c
@@ -5,8 +5,6 @@
  */
 
 /*\
- * [Description]
- *
  * Test allow to mount beneath top mount feature added in kernel 6.5:
  * 6ac392815628 ("fs: allow to mount beneath top mount")
  *
@@ -14,9 +12,10 @@
  * https://github.com/brauner/move-mount-beneath
  *
  * See also:
- * https://lore.kernel.org/all/20230202-fs-move-mount-replace-v4-0-98f3d80d7eaa@kernel.org/
- * https://lwn.net/Articles/930591/
- * https://github.com/brauner/move-mount-beneath
+ *
+ * - https://lore.kernel.org/all/20230202-fs-move-mount-replace-v4-0-98f3d80d7eaa@kernel.org/
+ * - https://lwn.net/Articles/930591/
+ * - https://github.com/brauner/move-mount-beneath
  */
 
 /*
@@ -68,7 +67,6 @@
  *           --/mnt    /DIRA /DIRB
  *         Check content of /DIRB, you can see file A exist since
  *         current /DIRB mount source is already become /DIRA
- *
  */
 
 #include <stdio.h>
@@ -142,4 +140,8 @@ static struct tst_test test = {
 	.needs_tmpdir = 1,
 	.setup = setup,
 	.cleanup = cleanup,
+	.tags = (const struct tst_tag[]) {
+		{"linux-git", "6ac392815628f"},
+		{}
+	},
 };

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2025-02-21 10:35 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
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 [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=20250221103519.GA2764810@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox