From: Wei Gao via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] mount_setattr02.c: Check mount_setattr attr.propagation
Date: Wed, 19 Feb 2025 04:51:12 -0500 [thread overview]
Message-ID: <Z7WpkIMnaQPb5yeh@wegao> (raw)
In-Reply-To: <20250219090536.GB2544812@pevik>
On Wed, Feb 19, 2025 at 10:05:36AM +0100, Petr Vorel wrote:
> > On Tue, Feb 18, 2025 at 04:18:58PM +0100, Petr Vorel wrote:
> > > Hi Wei,
>
> > > nit: I guess you want to replace dot with space in subject.
> > You mean i s/attr.propagation/attr propagation ?
>
> Yes.
Will update it in v3
>
> ...
> > > > +#define DIRA "/DIRA_PROPAGATION_CHECK"
>
> > > Is it necessary to to use directory under root?
> > Yes. Otherwise failed will happen during mount_setattr.
> > But i have not check for detail.
>
> Ideally we would create files in TMPDIR. Specially if bug in the code leave
> /DIRA_PROPAGATION_CHECK kept.
Got it, will try using TMPDIR and investigate why it report error.
>
> > > ...
> Sure, it should not block your work on the test.
>
> Kind regards,
> Petr
>
> > > Kind regards,
> > > Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-02-19 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 2:04 [LTP] [PATCH v1] mount_setattr02.c: Check mount_setattr attr.propagation Wei Gao via ltp
2025-02-18 15:18 ` Petr Vorel
2025-02-19 8:47 ` Wei Gao via ltp
2025-02-19 9:05 ` Petr Vorel
2025-02-19 9:51 ` Wei Gao via ltp [this message]
2025-02-19 11:24 ` Petr Vorel
2025-02-19 8:29 ` [LTP] [PATCH v2] " Wei Gao via ltp
2025-02-21 12:54 ` Petr Vorel
2025-02-24 1:44 ` Wei Gao via ltp
2025-03-19 11:41 ` [LTP] [PATCH v3] mount_setattr02.c: Check mount_setattr attr propagation Wei Gao via ltp
2025-07-11 9:21 ` Cyril Hrubis
2025-07-24 13:40 ` [LTP] [PATCH v4] " Wei Gao via ltp
2025-07-28 15:37 ` Cyril Hrubis
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=Z7WpkIMnaQPb5yeh@wegao \
--to=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--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