From: Wei Gao via ltp <ltp@lists.linux.it>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] chdir01.c: set umask to 0 within setup
Date: Thu, 7 Mar 2024 18:21:06 -0500 [thread overview]
Message-ID: <ZepL4jcbj6zmc0E1@wegao> (raw)
In-Reply-To: <6285aaad-79ca-4d7c-8be0-6d846d165df2@suse.cz>
On Thu, Mar 07, 2024 at 04:18:35PM +0100, Martin Doucha wrote:
> Hi,
> you're trying to fix a vfat mount quirk. We should fix that in the LTP
> library instead, e.g. by setting umask(0) and then restoring the original
> value inside safe_mount().
Thanks for your feedback.
For chdir case i just use Petr's below suggestion(Detail info you can check patch link
in below):
"2) tests, which set .mount_device = 1 and have more restrictive umask will not
work. Workaround would be to not use it and mount manually in the setup().
Or, reset umask with umask(0)."
https://patchwork.ozlabs.org/project/ltp/patch/20240219134845.22171-1-wegao@suse.com/
BTW: for similar issues we also do fix within test file in stead of lib such as:
https://patchwork.ozlabs.org/project/ltp/patch/20240303103105.13401-1-wegao@suse.com/
https://patchwork.ozlabs.org/project/ltp/patch/20240301102347.3035546-1-liwang@redhat.com/
> --
> Martin Doucha mdoucha@suse.cz
> SW Quality Engineer
> SUSE LINUX, s.r.o.
> CORSO IIa
> Krizikova 148/34
> 186 00 Prague 8
> Czech Republic
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-03-07 23:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 10:46 [LTP] [PATCH v1] chdir01.c: set umask to 0 within setup Wei Gao via ltp
2024-03-07 15:18 ` Martin Doucha
2024-03-07 21:33 ` Petr Vorel
2024-03-07 23:08 ` Petr Vorel
2024-03-07 23:21 ` Wei Gao via ltp [this message]
2024-03-08 9:31 ` Martin Doucha
2024-03-11 14:11 ` Petr Vorel
2024-03-08 8:32 ` [LTP] [PATCH v2] safe_macros.c: set umask to 0 within safe_mount Wei Gao via ltp
2024-03-08 9:16 ` Petr Vorel
2024-03-08 10:00 ` Martin Doucha
2024-03-15 10:31 ` 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=ZepL4jcbj6zmc0E1@wegao \
--to=ltp@lists.linux.it \
--cc=mdoucha@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 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.